Segregate internal client wireless from a guest wireless using WAP321
I am setting up a new network that will include at least 3 but as many as 6 WAP321 Wireless Access Points.
I used the wizard to set them up and all seemed well. I then went in to see how effective they were and discovered that the only difference between the internal network for the company and the guest network was the login and password. I could open and browser, type in an ip on the quest network and it went right to whatever it was pointed at on the network, (switch, firewall, server, whatever). This alarmed me because I could see someone using an ip scanner, picking up these ips and then causing major havoc. I had assumed there would be some kind of auto segregation when the wizard asked if I wanted setup my quest network. So I then went in and assigned different VLAN IDs on the access point and then set the VLANs on the switch and configured the (sorry guys not my choice) Sonicwall appliance to segregate. Does not work.
Is there a way via ACL or something on the WAP321 or do I need to configure something elsewhere to keep them segregated. I am not good (yet) with ACLs and have tried to figure that out but to no avail.
Article ID:5727 Configure the Single Point Setup on the WAP581 Objective
A Wireless Access Point (WAP) connects to a router and serves as a node
to the Wireless Local Area Network (WLAN). Clustering is when multiple
WAPs are joined on the same network. Th...
Article ID:5706 Upgrade the Firmware on the WAP125 Objective New
firmware releases are improvements from previous firmware versions.
Network device performance can be enhanced when an upgrade is made.
Firmware files can be downloaded through: Trivial File...
Article ID:1972 Configure Time Settings on a Wireless Access Point
Objective The system clock provides a network-synchronized time-stamping
service for software events such as message logs. Without synchronized
time, accurate correlation of log files betw...