Block inter-LAN routing when ER605 is managed via Omada Controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Reminding the team about this one. https://community.tp-link.com/en/business/forum/topic/540440
Request: The ability to block inter-LAN routing when using Omada Controller. As of 17/12/22, this is not implemented.
I had a customer yesterday complain that people using their guest network (on a seperate VLAN) is able to access a NAS on the main network. As they do not have any smart switches at all to configure additional VLAN's, I was not able to block access via a gateway ACL. A block was put in the NAS's security settings to block access to the guest subnet but this should not be required. There is other devices that "guests" do not need access to as well that do not have this feature.
Do you mean the function like below:
If so, the new firmware version of controller is already supported, but we need to wait for the release of the new firmware for ER605 adapted with V5.6 before we can do it.
@Virgo Does that work without an accompanying TP-Link Omada switch? If so, then yes.
E.g I've got an ER605 V2, LAN1 goes to my server running Hyper-V that has a virtual switch on a VLAN. Right now, I can ping between the 2 LAN's with a policy to stop it.
OR
Customer has a Ubiquiti AP connected to LAN2 broadcasting 2 SSID's. One of them is on a VLAN for guests however even though it has a different IP range, guests can still access the main LAN even with 2 gateway policies to block them.
