Cisco Cisco WAP121 Wireless-N Access Point with Single Point Setup Notas de publicación

Release Notes for the Cisco WAP121 and WAP321 Wireless Access Points

7

CSCtx60443

Captive Portal fails to authenticate WLAN clients if the Captive Portal-

enabled VAP interfaces and the AP management VLAN are assigned different IP subnets 
while Inter-VLAN Routing is disabled. 

Dedicate a single WAP321 for Captive Portal hotspot service with a 

different VLAN subnet network. 

Another workaround is to enable Inter-VLAN Routing and apply 

advanced access control lists (ACLs) on the connected router, and purposely 
segregate the AP management VLAN from other VLANs assigned on Captive Portal-
enabled VAP interfaces. 

CSCtx68659

Bonjour does not operate at the very first bootup of the WAP321 device. 

Even though the Bonjour feature shows enabled on the configuration utility, Bonjour-
enabled browsers or Cisco FindIT cannot access the WAP321 device.

Manually reset the WAP321 by pressing the Reset button on the 

device. Once the device is rebooted, the Bonjour name can be accessed by Bonjour-
enabled browsers or Cisco FindIT.

CSCtx08343

The DHCP process fails to retrieve a new IP address if the WAP device is in 

operation and the LAN cable is moved from one LAN to another. 

Reconnect the LAN cable back to old network and click Restart from 

the web-based configuration utility. Move the LAN cable immediately to the new LAN 
network after clicking Restart.

CSCtx04467

 When DHCP connectivity is changed to a static IP address, the browser will 

not automatically redirect the web-based configuration utility to the new IP address. 

Type in the new static IP address into the URL field to login again.