We have an SSID set-up as a guest network to prevent clients connecting to each other, and I note that the Omada series also blocks access to items on the LAN. (Unlike my previous AP.)

We have the typical 192.168.0.0/24 set-up and can access the internet without problem, but not connect to the management interface of switches through which the traffic passes. So far so good and as expected.

I have a server on 192.168.1.9 on another /24 subnet. This has a static route in the router to ensure that is reachable via a computer on the 192.168.0.0/24 subnet which does the inter-LAN routing.

Wired clients can connect to web servers etc. on 192.168.1.9 without issue.

E.G. 192.168.0.10 reaches 192.168.1.9 via the default gateway (192.168.0.128) which sends the traffic to 192.168.0.9 (static route on router) --> 192.168.0.9 passes the traffic to 192.168.1.9. All works as expected.

This fails on wireless clients on the EAP110 guest SSID. Why?

192.168.1.1 is not in the local subnet so it should pass the traffic to the default gateway like an Internet connection. After that, it's up to the default gateway's router to route the traffic. The EAP should not be able to detect anything different to a route around the Internet.

It's like the EAP110 is blocking inter-client LAN traffic based on something other than it being in the local sub-net. But what other definition is there?

Does anyone know what may be going on, please?