No IPs assigned for custom VLANs
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I am building a new home network using the controller OC200, TL-SG3210XHP-M2 for switch and two access points EAP650-Wall(EU) v1.0.
For my main LAN I am using the DHCP of the modem router provided by the ISP (192.168.7.x/24), gateway IP 192.168.7.1
Then using the interface of the OC200 I am setting the default LAN netowork as follows:
Then I would like to create a second VLAN for, let's say, for IoT devices. So I have created another LAN network as follows:
Finally I have created a corresponding wireless network for IoT and set its VLAN to the IoT LAN id: 27
Now to test the network I tried to connect my mobile to the SSID of my wireless IoT network. But it does not connect.
I get no IP from the DHCP (I would have expected something in the range of 192.168.27.x).
Most tutorials on setting up VLANs show these steps, however it does not seem to work for me... What am I missing?
thank you.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Steogen
Thanks for posting in our business forum.
Steogen wrote
Hi @Clive_A
Thanks for the tips. I will need a router, makes sense.. any suggestions for a suitable router? ER605 ok?
Only if you need an Omada router. I am not saying that you cannot use other routers if they support VLAN interfaces. As long as they support, configure the VLAN interfaces on them and this VLAN config on the Omada Controller would take effect as well.
But, if you would like to make this happen easily, you can use an Omada router which simply configure the VLAN interfaces in the LAN settings and you can make it work as expected.
If you intend to have long period of product life, I would suggest you purchase a better model. If you go for the cheap solution, ER605 V2 would suffice for most basic features.
- Copy Link
- Report Inappropriate Content
Hi @Steogen
Thanks for posting in our business forum.
Steogen wrote
@Mickman99 thanks. How would I do that? Is there a guide somewhere I can follow?
His answer is not quite accurate.
If you are going to get an IP, that's easy. Read this article: How to build up a multi-nets network via Multi-Nets NAT feature on TP-Link router with L2+/L3 switches
The old and vintage way to perform a DHCP server on the L3 switch. It's easy to do.
But do you need the Internet? If you need it, then you need the router to perform the NAT. Then you need a function called multi-nets NAT. Well, is this feature available on your existing router? If no, then you still need to get a router capable of that to do this.
I simply pointed you in the right direction where you should easily do this with the Omada solution.
He's using open-source router software and he can either set up the VLAN interface on his router or set up the VLAN and NAT on the router then set up the switch as the DHCP server and perform the IP assignment.
You should take a look at your current device before moving to the next step.
Also, the VLAN interface and 802.1Q VLAN are different. Google this and you can easily find the answers. FAQ provided above is 802.1Q VLAN, not the interface created on the router.
- Copy Link
- Report Inappropriate Content
Hi @Steogen
Thanks for posting in our business forum.
What router and switch do you use? The router, is it an Omada one?
Switch, is it 3210XHP-M2 V1?
Simply setting up the VLAN interfaces and creating a VLAN SSID would not make it work until you fix the problem on your router.
What you created in the pictures are VLAN interfaces which require the Omada router. If you don't have an Omada router, then your configuration would not work in that way. It simply means nothing to the switch. The interfaces are created on the router.
By default, the controller enables the switch to access all the VLANs. So, the configuration so far looks good. You miss the key point that you don't have an Omada router.
So, configure the VLAN interfaces on your router if it supports and you can still use it in this way.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Thanks for the tips. I will need a router, makes sense.. any suggestions for a suitable router? ER605 ok?
- Copy Link
- Report Inappropriate Content
Hi @Steogen
Thanks for posting in our business forum.
Steogen wrote
Hi @Clive_A
Thanks for the tips. I will need a router, makes sense.. any suggestions for a suitable router? ER605 ok?
Only if you need an Omada router. I am not saying that you cannot use other routers if they support VLAN interfaces. As long as they support, configure the VLAN interfaces on them and this VLAN config on the Omada Controller would take effect as well.
But, if you would like to make this happen easily, you can use an Omada router which simply configure the VLAN interfaces in the LAN settings and you can make it work as expected.
If you intend to have long period of product life, I would suggest you purchase a better model. If you go for the cheap solution, ER605 V2 would suffice for most basic features.
- Copy Link
- Report Inappropriate Content
you can make DHCP on the switch
- Copy Link
- Report Inappropriate Content
@Mickman99 thanks. How would I do that? Is there a guide somewhere I can follow?
- Copy Link
- Report Inappropriate Content
Hi @Steogen
Thanks for posting in our business forum.
Steogen wrote
@Mickman99 thanks. How would I do that? Is there a guide somewhere I can follow?
His answer is not quite accurate.
If you are going to get an IP, that's easy. Read this article: How to build up a multi-nets network via Multi-Nets NAT feature on TP-Link router with L2+/L3 switches
The old and vintage way to perform a DHCP server on the L3 switch. It's easy to do.
But do you need the Internet? If you need it, then you need the router to perform the NAT. Then you need a function called multi-nets NAT. Well, is this feature available on your existing router? If no, then you still need to get a router capable of that to do this.
I simply pointed you in the right direction where you should easily do this with the Omada solution.
He's using open-source router software and he can either set up the VLAN interface on his router or set up the VLAN and NAT on the router then set up the switch as the DHCP server and perform the IP assignment.
You should take a look at your current device before moving to the next step.
Also, the VLAN interface and 802.1Q VLAN are different. Google this and you can easily find the answers. FAQ provided above is 802.1Q VLAN, not the interface created on the router.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 639
Replies: 7
Voters 0
No one has voted for it yet.