Software Release Notes for firmware v3.0.0.7

Supported Products: WNDAP350, WNDAP360, WNDAP320, WNAP210v2, WNDAP660

READ THIS BEFORE ATTEMPT TO UPGRADE

If you are using a NETGEAR access point managed by wireless controller (WC7520, WC7600 or WC9500), do NOT upgrade to this firmware.

Prior to upgrade to v3.0.0.7, the device MUST be running the firmware version indicate in the table below. Upgrading from older firmware version to v3.0.0.7 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.

V2.x firmware images for the product can be downloaded from the NETGEAR Global Download Center

Firmware upgrade from v2.x to v3.0.0.7 will take about 7 minutes. Upgrade from v3.x to v3.x will take about 2 minutes.

Please see table below for upgrade requirement from older v2.x firmware to the latest v2.x firmware.

Once the device is upgraded to v3.0.0.7, it is NOT possible to downgrade the firmware back to v2.x except on WNDAP350.

To connect to CLOUD after upgrading to V3.0.0.7

1. Make sure the AP is able to access internet before upgrading the cloud image from standalone AP image so that it will try to connect to CLOUD BCWM after upgrade.
2. After connected the AP to CLOUD, AP configuration done through Local AP GUI, CLI interface (Telnet/SSH) and SNMP interface (MIB Browsers) is not allowed. Changes done using the CLOUD BCWM (Business Central Wireless Manager) will overwrite changes done using the AP user interfaces.
3. DHCP client will be enabled by default in the CLOUD image after doing factory defaults.

To be in standalone AP mode only after upgrading to V3.0.0.7

1. Log into the device Web UI. Go to the CLOUD tab and click “Disable”.
2. DHCP client will be enabled by default in the CLOUD image after doing factory defaults.

New Features available in this CLOUD + Standalone AP support release

1. Captive portal
   1. CP redirection supported only with accessing HTTP based website (Except HTTPS)
   2. Blocking HTTPS pages and specific protocol like HTTPS, FTP, Skype, Outlook, Internet applications from the wireless clients before authenticating with captive portal credentials.
   3. Allowing specific protocols like PING, RADIUS, DNS, DHCP from the wireless clients before authenticating with captive portal credentials.
2. VAP based MAC ACL from CLOUD
   1. VAP based MAC ACL with Allow and Deny policy
3. IP Roll back feature - User can choose to force new IPaddress settings from CLOUD or they can choose to keep the existing IPaddress settings in the AP
4. CLOUD tab in the AP local GUI to control CLOUD settings (enable / disable)
5. System monitor process to monitor and restart important process when got killed abruptly
6. Notifications related to the AP will be displayed in the CLOUD when activated with CLOUD.
7. AP enforces change of password when logged in with default password
8. Authentication passphrases and Keys are stored in encrypted form in the AP configuration database

Features not supported in CLOUD Connected mode

1. WDS
2. Client mode
3. Packet capture
4. STP (Spanning Tree Protocol)
5. QoS classification feature
6. IDS/IPS (Intrusion detection system / Intrusion protection system)
7. User Accounts
8. Dynamic VLAN
9. Band Steering

Configurations not supported from CLOUD BCWM (Business Central Wireless Manager)

1. Configuration of QoS – Basic and Advanced settings
2. Configuration of Wireless advanced settings (AMPDU values, Preamble, etc.,)
3. Disabling LLDP (Link layer discovery Protocol)
4. Disabling of 802.11d

Standalone mode - Known issues

1. WNAP210v1 AP is not supported for this CLOUD + Standalone AP release
2. Downgrade support is not available from V3.0.0.7 build to M2 build for all the CLOUD + Standalone supported products except WNDAP350 AP. Have to do factory reset if downgrade is initiated.
3. 11AC Stations disconnecting frequently from 360 AP
4. WNDAP360 AP getting low throughput with Intel 6300 station in UPLINK direction for 11NA CWM mode 40Mhz
5. In WNDAP660 AP 11NA mode throughput fluctuates frequently.
6. Sometimes in 660AP, P2P Ping connection fail when the WDS Authentication is changed from Open to WPA-PSK
7. SNMP process gets killed when WALK performed multiple times on the whole MIB tree and on the rogue AP "APlist"
8. Not able to disable the DHCPv6 server when hotSpot is enabled in WNDAP660 AP only
9. WNDAP350- Glitches would be seen by wireless clients when streaming HD multicast video
10. The data traffic over WDS will not happen with WPA-PSK and WPA2-PSK authentication when “Enable Client association” option is disabled. After reboot the data traffic works fine
11. AP goes to inaccessible state and wireless stations will experience disconnection when there is around more than 400Mbps of traffic (Unicast, multicast) from wired to wireless and vice versa ran for 8 – 10hrs continuously.
12. WNAP210v2 AP rogue AP scanning may not list neighbour APs properly which are in other channels
13. Chrome browser limitation – Crash observed when leaving the popup dialog for long time without clicking any option “OK” or “cancel” button. This issue doesn’t happens with V31.0.1650.63 and happens with latest V43.0.2357.124.

CLOUD mode - known issue

1. AP will reboot and configurations will be overwritten when any configuration is made in the cloud managed AP through SSH / local GUI / SNMP interface. This is as per the design.
2. Hard /Soft factory reset may be required when the CLOUD option is disabled/enabled in the local AP GUI when the AP is in CLOUD activated and connected state.
3. Very rarely wireless client got direct internet access  after doing kick MAC through cloud and then it connects back
4. Auto RF may not select best channel as expected
5. Auto RF may not doesn’t calculate channel for all the APs in the location
6. Rarely observed “Max client exceeded” notification appears in CLOUD WMS though the wireless clients are less than the Max client configuration
7. IP address of STA in notifications is empty when STAs are configured with Static IP address (Same and different subnet from AP) without gateway IP address. So the CLOUD monitoring page shows “0.0.0.0” for Wireless STA IPaddress

CLOUD BCWM (S10.27) - known issues

1. "Users connected now" of Usage sub-field under Location dash board showing Zero even though clients connected.
2. Unassigned AP's local Password settings under Account->Settings->"Account Settings" are not randomly generated yet.
3. No Grouping Option on the Monitoring > Location > Wireless Networks
4. After 5 unsuccessful account login attempts, the account will be locked out for 5 minutes as a security measure which is as per the design.
5. Wireless station association details are not available after downloading the event logs.
6. The BMP Image in the preview window of Edit Splash page loads slowly
7. The Duration showed in the CP logout window in the wireless station changes only on every 10 minutes.

Click on the following links to download the v3.0.0.7 image