This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.er7206 vlan without a switch
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Reviving a closed thread: https://community.tp-link.com/en/business/forum/topic/265578
At the time it seems that it was determined that the er7206 could NOT support vlan itself when using the omada controller, and that an omada supported switch was required. However, there were also talks of firmware updates potentially adding this ability.
Can someone confirm whether or not the er7206 will support vlan isolation on it's ports when using the omada controller WITHOUT an omada managed switch?
I have multiple APs, but only a few wired connections, and the er7206 would suffice if this is now possible.
@Clive_A Thanks for the technical lesson 
I was merely trying to understand if the er7206 received any firmware updates to allow the omada controller to manage separated networks on the physical ports as it does with managed switches. In the thread I mentioned, it seems that from anecdotal evidence that this did not work, but that there was potential for a firmware update that might.
That said, I think I see what you're saying. eg. two APs on separate networks connected on two separate ports in the er7206 would mean that the controller (connected on a different port) would only be able to reach one of them (assuming it is on the same network as one of them).
From your description, that feels like you need Management VLAN. That's isolation. But you said I am responding like a robot. That's offensive to me.
I think you should tell the difference between 802.1Q VLAN and VLAN interface before considering VLAN isolation. There are different ways to achieve isolation, ACL with VLAN interface, 802.1Q VLAN, and Management VLAN. That's all we have for the devices now. Which one do you want to use? What goal do you want to achieve?
Management VLAN can also achieve that if you want to isolate clients from AP, router, and router. But Management VLAN includes these core devices into the same network(VLAN) and makes them stay in the same subnet.
If you set AP to a different VLAN interface, you can still adopt it but requiring you to use Omada Discovery Utility or DHCP Option 138.
If you set AP to a different 802.1Q VLAN(Purpose = VLAN), then you don't have access at all. But I don't see anyone use this because you lose control to your devices.
What you revived is an old post asking for a feature to have the ability to set up PVID. Is that what you looking for? It was added several versions before.
