The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
RV160x/RV260x Language Selection User Interface Anamoly
Defect Reference ID: CSCus75139
June 3, 2015
August 15, 2018
Intermittently the wireless client doesn't get an IP from the DHCP server.
The WAP321 stops forwarding DHCP traffic after some time on one SSID when the DHCP responses from the Server are broadcast instead of unicast.
The WAP321 is running for some time and the DHCP server responds to DHCP requests as broadcast messages.
A temporary solution can be found if you reboot the device. If the issue happens to all SSIDs, then you can configure the DHCP server to use a Unicast Message.
For instructions on how to reboot the WAP, click here.
Download and Update to the latest firmware Version, which is currently 184.108.40.206
Shortcut to the latest WAP321 Download Page
To be brought directly to the WAP321 Download page, click here.
Step by Step Instructions for Downloading Firmware for any Device
Step 1. To find the current version for any of your Cisco devices, go to Cisco and select MENU on the upper left corner of the screen.
Step 2. Select Support and Downloads.
Step 3. The screen will expand and you can enter the model number of your device, in this case WAP321 would be entered and then selected from the drop-down menu.
Step 4. Select Downloads.
Step 5. Select the latest version.
Step 6. It will save to the Downloads folder on your computer.
Step 7. For instructions on getting the firmware onto the WAP321, click here.
Upgrading the firmware eliminates the bug from appearing again.