IP-adres when using the portal for guest-wifi
Team,
We have assigned wifi guest access to vlan 100.
And of course, this includes a different subnet for guest access.
The management is in vlan-1.
However, guests are still trying to connect to the management-vlan-IP-adres of the controller as being the portal
Versus the vlan-100 IP-adres of the controller (i.e. where the portal resides for that specific vlan).
For example - the management vlan is 192.168.9.0/24.
The default gw is 192.168.9.240. The controller, the wifi-guest-portal and the DNS-server are running on the same VM with ip 192.168.9.235.
For vlan-100 this 9-subnet is replaced with 192.168.100.*/24.
This includes the default gw (i.e. .100.240), the controller, the wifi-guest-portal and the DNS-server (all three are .100.235)
The Omada-cloud portal shows all the vlan IP's. Meanung it looks like the controller is vlan aware?
How do I enforce the wifi-guest-clients to use the portal-IP-address of vlan-100?
With warm regards - Will