No way to isolate AP clients without isolating from other subnets
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I need my AP clients to be isoalted between each other, but with possibility to reach a chosen IP in LAN (outside AP, wired one) - a network printer.
It is currently not possible to achieve this in Omada.
The "Guest network" enabled in wifi isolates too much. It isolates AP clients - good, BUT it also isolates AP clients from the network printer - BAD. No way to bring the connectivity back.
On the other hand, ACLs do not work when trying to isolate clients connected to the same SSID to the same AP - no way to isolate AP clients between each other.
This is a regression to te feature available some months ago with possibility to "Isolate SSID" without isolating from all the other private IP subnets under the hood (10.0.0.0 - 10.255.255.255; 172.16.0.0 - 172.31.255.555; 192.168.0.0 - 192.168.255.255 ).
My stack - full omada, namely:
- router and controller: ER7212PC (latest available firmware: 1.1.1)
- access point: EAP610 connected to the above router (latest availabble firmware)
- the printer connected via LAN directly to the router
- clients connected to the access point via wifi
d0ugmac1 wrote
I tried that already (screenshots below) and the isolation unfortunately doesn't work. I tried both - "Switch ACL" and "EAP ACL". It seems like ACLs are not respected if 2 clients are connected to he same AP and the same SSID.
FWIW ACLs seem to be respected for clients connected to 2 different SSIDs (even if it's the same signle AP). But that's not my case.
I edited the original message with my full stack - full omada, namely:
- router ER7212PC
- access point: EAP610 connected to the above router
- the printer connected via LAN directly to the router