How to allow 2 vlans to share the same subnet?
Router - ER706W
Switch x2 - SG2210P
Controller - OC200
APs x9 - EAP650 wall mount
3 VLANS:
Default VLAN 192.168.8.1/23
Guest VLAN 88.88.88.1
For the 3rd VLAN which i intend to put as IoT VLAN, is it possible to share the same subnet as default vlan? as i wish for my IoT VLAN to use only DHCP range from 192.168.9.100 to 192.168.9.200.
If its not possible. Is there a way for both vlans to communicate with each other?
Thankyou in advance and sorry for the grammer.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Evanloh2001
Thanks for posting in our business forum.
No. VLAN interface communicates by default.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Thankyou for replying!
If VLAN interface communicates by default.
Do i still need create a trunk port on the switch?
Currently i have IoT VLAN interface at 192.168.18.1/24. Example where my printer is on 192.168.18.1
Will my computer thats on 192.168.8.1 able to send documents to the printer?
Sorry as im not very knowledgeable in this. I hope you understand. Thankyou
- Copy Link
- Report Inappropriate Content
Hi @Evanloh2001
Thanks for posting in our business forum.
Evanloh2001 wrote
Hi @Clive_A
Thankyou for replying!
If VLAN interface communicates by default.
Do i still need create a trunk port on the switch?
Currently i have IoT VLAN interface at 192.168.18.1/24. Example where my printer is on 192.168.18.1
Will my computer thats on 192.168.8.1 able to send documents to the printer?
Sorry as im not very knowledgeable in this. I hope you understand. Thankyou
The trunk has nothing to do with the VLAN interface. Trunk is a concept in 802.1Q VLAN.
Read this:
There are docs about the VLAN and you should get yourself familiarized with them as you proceed with the config and VLAN tag.
They can communicate if they are in the same subnet. Or a different subnet(VLAN interface) by default(without ACL or any block rules) but mDNS might be needed for discovery.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
Really appreciate your quick reply!
So yes even with different interface they can communicate but may need nDNS to discover it.
Okay. I will look into the vlan document you sent as well as nDNS.
Thankyou so much for the time!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 119
Replies: 4
Voters 0
No one has voted for it yet.