While what I am fixing to share is not in any way a great solution, It can be utilized as a workaround.
With the WAP321, after trying a few different scenarios that didn’t work. I simply set with two vlans, attached Guest vlan to the Guest SSID and changed the Management VLAN to match the Guest vlan ( In my case 2). This allowed me to authenticate to my guest SSID portal and get an IP and get out to the internet. The Main SSID still worked normally.
Now for some caveats:
Problem: If a wireless client knows the IP of the WAP and the username and password they could get into the WAP.
Solution: Setup Management Access Control to an IP outside the DHCP scope for that VLAN and have a Strong Password.
Problem: Management of the WAP321 can only be from an IP on the Management VLAN. (In my case 2)
Solution: Setup Management Access Control to an IP outside the DHCP scope for that VLAN and have a Strong Password.
Not the very best solution, but the only workaround I can come up with for now.
Thanks
Eric Moyers .:|:.:|:.
Cisco Small Business US STAC Advanced Support Engineer
Wireless Subject Matter Expert
CCNA, CCNA-Wireless
866-606-1866
Mon - Fri 09:30 - 18:30 (UTC - 05:00)
*Please rate the Post so other will know when an answer has been found.
