As the title says, we are running a guest wifi on a separate vlan, which causes the management IP to unleashed to be unavailable.
This is clearly a design flaw of the system, why offer vlan options if you can't use it for this. Cannot use guest wlan option under a separate vlan at all due to this.
This is clearly a design flaw of the system, why offer vlan options if you can't use it for this. Cannot use guest wlan option under a separate vlan at all due to this.
silent
Even in your scenario i think the management ip is not available on the guest vlan. Also this is a security risk opening up to have the management IP available to the guest network.
GITM
Set the ports on the switch as Trunk 802.1q and allow VLANs 30 (employees) and 60 (guest). Set native VLAN to 30.
Set IP addresses for the APs on the xx.xx.30.xx subnet.
Under WLAN setup, set the access VLAN to 1 for the employee SSID and 60 for the guest SSID.
Restrict subnet access on the guest SSID.
I can manage my APs through the employee network, but not through the guest network.
silent
I have the vlan working for normal networks, when i introduce 'guest mode' where it's prompting the user to accept to terms is where my issue lies, since that is done via the management IP address of the AP/Unleashed.
GITM
silent