NOTE: Before upgrading to 3.5.6.0, please see the upgrade process in detail.
Bug Fixes
- Improved Captive Portal redirection time in Business Central mode
Known issues
- Hotspot works when the wireless network is configured with default VLAN ID only..
- Rogue AP table may not list all neighbor APs.
- There are known wireless client connectivity issues with MacBook Pro running with V10.8.5 OS x (Mountain Lion), so highly recommends to upgrade latest OS to get better performance.
NOTES :
- The default IP address of the AP is 192.168.0.100. DHCP client is enabled by default.
- Cloud management Business Central 2.0 (BC 2.0) is supported in AP running with V3.5.5.0 or higher Firmware version (V3.5.x.x). By default Business Central mode is enabled.
- AP supports two modes of operation, Standalone mode and CLOUD mode (or Business Central Wireless Manager Mode).
- Enable/Disable Business central (Cloud Enabled) option resets the AP to factory default but retains IP, DNS and management VLAN settings.
- In the following scenarios AP is expected to reboot automatically for the configuration to take effect:
a. Change Country/Region
b. After Firmware upgrade
c. After Restore Configuration Settings
d. Reset factory defaults
e. Cloud enable/disable
In all the other conditions AP is not supposed to reboot automatically.
To Upgrade
- Download the new software and save it to a convenient folder location. The firmware filename after extracting is wnap320_firmware.tar
Download link : http://www.downloads.netgear.com/files/GDC/WNAP320/WNAP320_V3.5.6.0.zip
- Login to the access point web management GUI.
- Select Maintenance > Upgrade > Firmware Upgrade.
- Click Browse and browse to the location of the software upgrade file that you just downloaded.
- Click Apply. The upgrade process typically takes at least 3 minutes.
Warning: When uploading software to the WNAP320 Wireless Access Point, it is important not to interrupt the Web browser by closing the window, clicking a link, or loading a new page. If the browser is interrupted, the upload might fail, corrupt the software, and render the WNAP320 access point completely inoperable.
- When the upload is completed, your wireless access point automatically restarts.
- If you decide to use the AP as standalone image, log into the AP and disable Cloud management.
- If you decide to use the AP in cloud management, factory reset the AP and add the AP to BCWM portal (https://bc.netgear.com).
READ THIS BEFORE ATTEMPT TO UPGRADE
Prior to upgrade to v3.x, the device MUST be running the firmware version indicate in the table below. Upgrading from older firmware version to v3.x without the required running firmware version will cause the user not able to access the device Web interface. The only way to recover is by factory resetting the device.
| Case |
Notes
|
| Brand new AP to Standalone |
Disable Cloud management.
Download latest 3.5.x from support website.
Load it on the AP and use it as standalone from local AP GUI.
|
| Brand New AP with 3.0.x image to Business Central managed AP |
Download latest 3.5.x from support website.
Load it on the AP.
Factory reset the AP.
Add the AP to BC portal.
AP will automatically join BC once it has access to internet.
|
| Brand New AP with 3.5.x image to Business Central managed AP |
Factory reset the AP.
Add the AP to BC portal.
AP will automatically join BC once it has access to internet.
|
| Standalone to Business Central managed AP |
Download latest 3.5.x from support website.
Load it on the AP.
Factory reset the AP.
Add the AP to BC portal.
AP will automatically join BC once it has access to the Internet.
|
|
Working Standalone to Standalone
|
Case 1: AP running in 3.0.x can upgrade to 3.5.6.0 directly.
Case 2: AP running in 3.5.x can upgrade to 3.5.6.0 directly.
Case 3: AP running 2.x, first upgrade to 2.1.6. Then upgrade to 3.5.6.0
NOTE: Take back-up of the current configurations before any upgrade. Save it at a secure place.
|
FIRMWARE UPGRADE SEQUENCE TABLE
- AP running in 3.0.x can upgrade to 3.5.6.0 directly.
- AP running in 2.x should follow below sequence for firmware upgrade to 3.5.x.
|
S No
|
Product
|
RC 3-digit (M2) previous FW Version
|
RC 3-digit (M2) FW Version
|
RC 3-digit (M4) FW Version
|
Upgrade time
|
|
1
|
WNDAP660
|
2.0.0, 2.0.1, 2.0.2, 2.0.4
|
V2.0.5
|
V3.5.6.0
|
~ 3 minutes
|
|
2
|
WNDAP360
|
2.1.11
|
V2.1.12
|
V3.5.6.0
|
~ 3 minutes
|
|
3
|
WNDAP350
|
2.1.9
|
V2.1.9
|
V3.5.6.0
|
~ 3 minutes
|
|
4
|
WNAP320
|
2.1.5
|
V2.1.6
|
V3.5.6.0
|
~ 3 minutes
|
|
5
|
WNAP210v2
|
2.1.4
|
V2.1.5, V2.1.6
|
V3.5.6.0
|
~ 3 minutes
|
Note:
- Upgrade initiated from other 2.x firmware version is not supported. The side effect of the wrong firmware upgrade will block users to login to the AP and sometimes allow user to login but the page shows fatal error without any tabs. Doing manual factory reset by hardware buttons and also through SSH/Telnet will recover the AP from the side effect mentioned but the entire configuration will get lost.
Example firmware upgrade sequence for WNAP320 from 2.x:
V2.1.5 -> V2.1.6 -> V3.5.6.0 - Correct sequence
- Downgrade from v3.x versions to 2.x image is not supported without a factory reset.
- Firmware upgrade from v2.x to v3.0.x will take about 8 minutes. Upgrade from v3.x to v3.x will take about 2 minutes.
- V2.x firmware images for the product can be downloaded from the Netgear download center http://downloadcenter.netgear.com/
Method to factory reset the AP via CLI
Using putty/tera term telent/ssh to the AP and run “restore-configuration /etc/default-config” or “restore-factory-default”
This product includes software code developed by third parties, including software code subject to the GNU General Public License ("GPL") or GNU Lesser General Public License ("LGPL"). As applicable, the terms of the GPL and LGPL, and information on obtaining access to the GPL Code and LGPL Code used in this product, are available to you at NETGEAR's Open Source Code Web page. The GPL Code and LGPL Code used in this product is distributed WITHOUT ANY WARRANTY and is subject to the copyrights of one or more authors. For details, see the GPL Code and LGPL Code for this product and the terms of the GPL and LGPL.