Cisco Cisco WAP321 Wireless-N Access Point with Single Point Setup Notas de publicación
Release Notes for the Cisco WAP121 and WAP321 Wireless Access Points
3
Release Notes
Resolved Issues
CSCub46649—While operating WDS Bridging using a 2.4 GHz band with a 20/40
MHz channel bandwidth, the WDS links may disconnect. The radio can change
from 40 MHz to 20 MHz if any 20 MHz devices are detected in the area, resulting in
a mismatch of channel bandwidths throughout the WDS devices.
MHz channel bandwidth, the WDS links may disconnect. The radio can change
from 40 MHz to 20 MHz if any 20 MHz devices are detected in the area, resulting in
a mismatch of channel bandwidths throughout the WDS devices.
CSCud39468—Mobile device users received HTTP 404 with Captive Portal.
Open Caveats
Table 1 Open Caveats in Firmware Version 1.0.3.4
Ref Number
Description
CSCue70448
Symptom:
Deleting an SNMP group (related with a user1) prevents the addition of any
other SNMP users unless user1 is first deleted.
Workaround:
Delete the group and all users in the group at the same time.
CSCue51459
Symptom:
Unable to a redirect URL in a captive portal instance.
Workaround:
Use a URL path without extensions at the end of the URL.
CSCue24521
Symptom:
Some clients may lose wireless connection when authenticating via
Captive portal.
Workaround:
Reconnect wireless devices.
CSCub46043
Symptom:
When untagged packets are received on a VAP interface (SSID), they may
be treated as tagged packets.
CSCub45975
Symptom:
In a radio saturated environment, Work Group Bridge mode can take from
three to seven minutes to establish connectivity with the remote upstream access point.
CSCtx04467
Symptom:
When DHCP connectivity is changed to a static IP address, the browser
does not automatically redirect the web-based configuration utility to the new IP
address.
address.
Workaround:
Type in the new static IP address into the URL field and login again.