Interface vs. VLAN - a bit confused?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
First let me explain what I'd like to do:
I'd like to have a management VLAN that cannot connect to the router to go out to the internet. Simple as that. Its only available externally and ideally through a wireless VLAN only so I can just jump on it from any of my wireless devices. (Hidden, of course.)
I go into Wired Networks>LAN and click on "Create New LAN" and have the choice of "Interface" vs. "VLAN" - and VLAN gives me far fewer options (no DHCP server, no interface to presumably route through, domain name, etc.)
I'm assuming this simply means that a VLAN is not routable externally (which is perfect for a management VLAN) but that I'd obviously have to provide a DHCP server for that VLAN (not a big deal, I can do that.)
I did look through the documentation for the OC200 as well as do a search on here, but of course I get all kinds of confusing results in a search, and nothing comes up in the OC200 documentation explaining the difference. If someone could point me to some documentation explaining the difference that would be awesome too.
The VLAN is based on the 802.1Q VLAN, to achieve network isolation, but currently the controller cannot set up the PVID, so in fact this option is not useful at this moment.
The Interface can provide more options such as set up DHCP range, and devices in different IP range can communicate with each other. To set up the isolation, currently only the ACL can do that.
The TP-Link website has instruction about how to set up VLAN interface and also using ACL to block the devices.
https://www.tp-link.com/us/support/faq/3091/