NOTE: Before upgrading to 3.7.4.0, please see the upgrade process in detail.

Bug Fixes

Known issues

NOTES:

  1. The default IP address of the AP is 192.168.0.100. DHCP client is enabled by default. 
  2. Cloud management Business Central 2.0 (BC 2.0) is supported in AP running with V3.5.5.0 or higher FW version. By default Business Central mode is enabled.
  3. AP supports two modes of operation, Standalone mode and CLOUD mode (or Business Central Wireless Manager Mode).
  4. Enable/Disable Business central (Cloud Enabled) option resets the AP to factory default but retains IP, DNS and management VLAN settings
  5. 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 Install

  1. Download the new software and save it to a convenient folder location. The firmware filename after extracting is WNDAP350_V3.7.4.0_firmware.tar.

    Download link : http://www.downloads.netgear.com/files/GDC/WNDAP350/WNDAP350_V3.7.4.0.zip
  2. Login to the access point web management GUI.
  3. Take backup of the current configuration and save it at a secure place. 
  4. Select Maintenance > Upgrade > Firmware Upgrade.
  5. Click Browse and browse to the location of the software upgrade file that you just downloaded and click APPLY button.
    Warning: When uploading software, 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 this AP completely inoperable.
  6. When the upload is completed, your wireless access point automatically restarts.
  7. If you decide to use the AP as standalone image, log into the AP and disable Cloud management.
  8. 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.7.x from support website.
Load it on the AP                     

Factory reset 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.7.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

Brand New AP with 3.5.x image to Business Central managed AP

Download latest 3.7.x from support website.                                    

Factory reset the AP.
Add the AP to BC portal.
AP will automatically join BC once it has access to the Internet

Standalone to Business Central managed AP

Download latest 3.7.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.5.x can upgrade to 3.7.4.0 directly.

Case 2: AP running in 3.0.x can upgrade to 3.7.4.0 directly.

Case 3: AP running 2.x, follow this recommended upgrade sequence: 2.1.9 -> 3.5.23.0 -> 3.7.4.0

NOTE: Take back-up of the current configurations before any upgrade. Save it at a secure place.

FIRMWARE UPGRADE SEQUENCE TABLE

  1. AP running in 3.0.x/3.5.x can upgrade to 3.7.4.0 directly.
  2. AP running in 2.x should follow below sequence for firmware upgrade to 3.7.x

S No

Product

RC 3-digit (M2) previous FW Version

RC 3-digit (M2) FW Version

RC 3-digit (M3) 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.23.0

V3.7.4.0

~ 3 minutes

2

WNDAP360

2.1.11

V2.1.12

V3.5.23.0

V3.7.4.0

~ 3 minutes

3

WNDAP350

2.1.9

V2.1.9

V3.5.23.0

V3.7.4.0

~ 3 minutes

4

WNAP320

2.1.5

V2.1.6

V3.5.23.0

V3.7.4.0

~ 3 minutes

5

WNAP210v2

2.1.4

V2.1.5, V2.1.6

V3.5.23.0

V3.7.4.0

~ 3 minutes

Note:

  1. Upgrade initiated except the 2.x firmware version mentioned from the above table is not supported. By doing so will block the 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.

         Example firmware upgrade sequence for WNDAP350 from 2.x:
            
    V2.1.8 -> V2.1.9 -> V3.5.23.0 -> V3.7.4.0 – Correct sequence
  2. Downgrade from v3.x versions to 2.x image will lead to the AP may not function properly which always required factory reset before doing any configuration..
  3. Firmware upgrade from any v2.x to latest v2.x will take about 8 minutes. Upgrade from v3.x to v3.x and latest v2.x to V3.x will take about 3 minutes
  4. 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.