Client isolation without private network filtering
Hello,
I recently deployed a custom captive portal implementation for our guest network of six Omada APs, unfortunately clients were unable to access the landing page running on a 10.x.x.x IP after connecting to the guest SSID. It seems when "Guest Network" is enabled on an SSID, the APs are also doing some kind of traffic filtering, as soon as I unchecked Guest Network, the portal started working again but obviously this means clients can also see each other. To get it working with Guest Mode enabled, I ended up hijacking a public IP and NATting client requests to it to the internal 10.x.x.x IP for authorization, which is obviously not ideal.
Is there a way to only have the client isolation portion of Guest Network take effect, or to customize what is being filtered? DNS and DHCP were getting through fine, but HTTP and HTTPS seem to be blocked.