New Features and Enhancements
- This is first image where Cloud management Business Central 2.0 (BC 2.0) is supported.
- The AP running 3.5.6.0 will support two modes of operation, Standalone mode and CLOUD mode (or Business Central Wireless Manager Mode). By default CLOUD mode is enabled.
- Netgear's Business Central portal (https://bc.netgear.com/) supports Configuration, management and monitoring.
a. Visit http://www.netgear.com/business/products/wireless/wireless-management/business-central.aspx to know all the features supported in this mode. - On Standalone and ensemble mode, new Dashboard graphs have been added under monitor page.
- 802.11K (RRM) that helps Wireless clients to decide better on which AP to join in multiple AP setup.
- Support for Europe Weather DFS channels in standalone mode.
- Enhanced user friendly messages while configuring captive portal.
Bug Fixes
- Multiple SNMP bugs have been fixed in standalone and ensemble mode.
- AP will not fallback to default IP if DHCP server is not reachable.
- Sorting functionality of Rogue AP's list in the monitoring page.
- Clients fails to connect to the wireless, if multicast traffic is running in the network.
- Appropriate error has to be thrown for Ensemble Firmware Upgrade when there is no member AP is selected.
- UCT shown instead of UTC in the current time.
Known Issues
- In statistics Page, the Tx packets and bytes are inclusive of Multicast & Broadcast packets in Dashboard.
- AP shows only first 20 clients when it work in Ensemble mode and it expects admin to go to individual AP to see on rest of the clients.
- When administrator configures one of the APs in the Ensemble, then the AP will push the configuration to the rest of the Ensemble and assumes the control of the Ensemble.
- No way to select which channels to be used (or not to be used) for Auto Channel Allocation feature in Ensemble mode. Right now, we are forced to use all the channels.
- For 5Ghz Auto-channel logic will select from all non-DFS allowed channels for the current country code/revision list.
- For 2.4Ghz Auto-Channel logic will select 1, 6, 11 and it is hard coded. - Unable to save the Known APs on Checking & Unchecking Known APs list.
- Ensemble: Negative values for wired/wireless traffic are seen for the master AP in the ensemble dashboard.
- Ensemble : Sometimes Incorrect Upstream/ Downstream traffic for the active clients.
- Using the Download Link below, download and extract the new firmware to a convenient place such as your desktop.
The Firmware File name after extracting is WAC720_WAC730_3.5.6.0.tar
Download Link: http://www.downloads.netgear.com/files/GDC/WAC720/WAC720_WAC730_V3.5.6.0.zip - Login to the AP web interface.
- Select Maintenance > Upgrade > Firmware Upgrade
- Click the Browse button and locate the image (.tar) upgrade file.
- Click the Apply button to initiate the upgrade process.
During the upgrade process, the wireless access point automatically restarts. The upgrade process typically takes several minutes. When the Test LED turns off, wait a few more seconds before doing anything with the wireless access point.
Upgrade Rules:
For Standalone and ensemble users
- If fresh out-of-factory AP, It is recommended to upgrade to latest image before starting to configure the AP for use and deployment.
- If fresh out-of-factory AP with V3.5.6.0 by default cloud mode is enabled, disable cloud mode to operate in Standalone/Ensemble mode.
- Before using your AP, ensure you are using the latest firmware and factory default before placing your AP in production.
- The AP will factory reset when it upgraded to V3.1.5.0 / V3.5.6.0 and will erase the configuration. Follow the steps mentioned below to restore the old configuration.
If the AP was configured before upgrading the AP to 3.1.5.0 / V3.5.6.0, then please
1. Do "config backup" in the current FW
2. Upgrade to 3.1.5.0 / V3.5.6.0
3. Restore backup. - To connect to BC 2.0 manager, you need to upgrade to V3.5.6.0 image.
NOTES:
- The default IP address of the AP is 192.168.0.100 when the AP cannot get dynamic IP address. DHCP client is enabled by default
- In the following scenarios AP is expected to reboot automatically for the configuration to take effect:
a. After Firmware upgrade
b. Reset factory defaults - Factory reset will be required if upgrading from 3.1.0.0 version via TFTP, or user want to convert standalone AP to controller mode.
.