Latest documentation and WaveManager versions are available from the Acksys website (www.acksys.com).
Version / date | Changes |
---|---|
4.12.2.1 14-Apr-2021 | Bug fixes |
4.12.1.1 25-Mar-2021 | Bug fixes |
4.12.0.1 3-Feb-2021 | Bug fixes and improvements |
|
|
4.10.1.1 12-Jan-2021 | Bug fixes |
4.10.0.1 12-oct-2020 | Bug fixes and improvements |
4.8.1.1 17-Aug-2020 | Bug fixes |
4.8.0.1 20-mar-2020 | Bug fixes and improvements |
| |
4.4.5.1 28-feb-2020 | Bug fixes |
4.4.4.1 13-dec-2019 | Bug fixes |
4.4.3.1 12-dec-2019 | Bug fixes |
4.4.2.1 14-nov-2019 | Bug fixes |
This version is only for AirLink, AirBox, AirXroad, EmbedAir100, EmbedAir1000, RuggedAir100, RuggedAir1000 | |
4.4.1.1 08-nov-2019 | Bug fixes and improvements |
4.4.0.1 09-oct-2019 | Bug fixes and improvements |
4.2.1.1 24-july-2019 | DFS channels fixes, log improvements |
4.2.0.1 05-july-2019 | Major version |
| |
4.0.0.1 Not released | Development version |
This version was not released. | |
3.18.4.1 25-Sep-2020 | Bugs fixes |
|
|
3.18.3.1 02-Apr-2019 | Bugs fixes |
3.18.2.1 06-Mar-2019 | Bugs fixes |
| |
3.18.1.1 19-Nov-2018 | Bugs fixes and improvement |
3.18.0.1 17-Oct-2018 | Bug fixes and improvement |
| |
3.16.1.1 3-July-2018 | Bug Fixes and improvement |
→This version does not contain fixes from version 3.14.6.1 and 3.14.7.1 | |
3.16.0.1 25-Apr-2018 | Improvement |
| |
3.14.7.1 9-Jan-2019 | Bug fixe |
| |
3.14.6.1 18-Dec-2018 | Bug fixes |
3.14.5.1 30-Aug-2018 | Bug fixes |
3.14.3.1 02-July-2018 | Bug fixes and improvement |
3.14.2.1 15-May-2018 | Bug fixes |
3.14.1.1 18-Apr-2018 | Bug fixes |
3.14.0.1 7-Mar-2018 | Improvements and bug fixes |
| |
3.12.14.1 5-Feb-2018 | bug fix |
| |
3.12.13.1 5-Feb-2018 | bugs fixes |
3.12.12.1 24-Nov-2017 | Improvement and bugs fixes |
3.12.11.1 16-Oct-2017 | Improvement and bug fixes |
3.12.10.1 21-Sep-2017 | Improvements and bug fixes |
3.12.9.1 30-Aug-2017 | Improvements and bug fixes |
3.12.8.1 12-july-2017 | Improvements and bug fixes |
| |
3.12.7.1 16-june-2017 | Improvements and Bug Fixes |
3.12.6.1 30-may-2017 | Improvements and Bug Fixes |
3.12.5.1 22-may-2017 | Improvement |
| |
3.12.4.1 11-may-2017 | Bug Fixes |
3.12.3.1 04-may-2017 | Improvements and Bug Fixes |
3.12.2.1 13-Apr-2017 | Improvements and Bug Fixes |
3.12.0.1 16-Mar-2017 | Improvements and Bug Fixes |
| |
3.10.2.1 31-jan-2017 | Bug Fixes |
| |
3.10.1.1 16-jan-2017 | Bug Fixes |
3.10.0.1 13-dec-2016 | Bug Fixes and MIB improvement |
| |
3.8.0.1 14-oct-2016 | Bug Fixes and Wln range support |
| |
3.6.0.1 23-July-2016 | Bug Fixes and improvement |
| |
3.4.2.1 12-Apr-16 | Bug Fixes and improvement |
| |
3.4.1.1 22-Mar-16 | RSTP improvement |
| |
3.4.0.1 09-Mar-16 | Bug fixes and Firmware improvements |
| |
3.2.0.1 27-Nov-15 | First WaveOS release |
|
Tracker# | found in versions | version corrected | Description / Countermesures |
---|---|---|---|
878 | 3.0.0.1 | 3.14.0.1 |
The OID statusPhyWifiScanTableUpdateTbl may return 'Available' when the scan is finished. →Update to 3.14.0.1 |
1432 | 3.2.0.1 | 3.8.0.1 |
With some web browser, it can be impossible to commit the wireless settings. →Update to 3.8.0.1 |
1480 | 3.2.0.1 |
It is not possible to send VLAN tagged frames through the WiFi interface. →use L2 GRE tunnel on wireless interface if you need to send VLAN tagged frames. |
|
1481 | 3.2.0.1 | 3.4.0.1 |
On RailBox/11, the connection between the AP and the sta can be dropped during the WPA rekeying. →Set the rekeying delay to 0. |
1506 | 3.2.0.1 | 3.4.0.1 |
On RailBox/11, the SAE security doesn't work. →Upgrade to 3.4.0.1 |
1537 | 3.2.0.1 | 3.4.0.1 |
The frame filter on GRE interface doesn't work. |
1543 | 3.2.0.1 | 3.4.0.1 |
The wireless clonning mode doesn't work |
1553 | 3.2.0.1 | 3.8.0.1 |
In some cases, it is possible to have an incomplete GRE tunnel configured, and it is not possible to delete it. |
1555 | 3.2.0.1 | 3.4.0.1 |
If the bridge VLAN feature is enabled on the bridge and a wireless interface is added in the bridge and the wireless interface uses the automatic channel select or DFS channel, the bridge VLAN settings are not applied. |
1562 | 3.2.0.1 | 3.4.0.1 |
The administrator password is not exported in the C-KEY nor the configuration file. |
1568 | 3.2.0.1 | 3.4.0.1 |
The wireless "g only" mode is not compatible between the WLg and Railbox series. →Use the "b/g" mode instead. |
1591 | 3.4.0.1 | 3.6.0.1 |
Access to the web interface with HTTPS protocol doesn't work. →Upgrade to 3.6.0.1 |
1629 | 2.8.0.1 | 3.12.0.1 | The scan result get from snmp, the latest mac address byte is missing. →Upgrade to 3.12.0.1 |
1637 | 3.4.0.1 | 3.4.2.1 |
If the password file is corrupted, the web interface access is not protected. The password can be corrupted if you change the password and power off the product, while the modifications are saved. →Upgrade to 3.4.2.1 |
1663 | 3.0.0.1 | 3.6.0.1 |
The https server is vulnerable to several SSL attack (Hearthbleed, CCS injection, Poodle, ...). →Upgrade to 3.6.0.1 |
1677 | 3.0.0.1 | 3.6.0.1 |
The settings backup file list are not the same between the C-Key and the web interface backup. →Upgrade to 3.6.0.1 |
1685 | 3.4.2.1 | 3.6.0.1 |
the "Wireless/channel status" web page is not available. →Upgrade to 3.6.0.1 |
1696 | 3.5.0.1 | 3.14.0.1 | The OID internalAlarmSwitch doesn't return the Switch status →Upgrade to 3.14.0.1 |
1719 | 3.6.0.1 | 3.8.0.1 |
In some cases, it is possible to have an internal error on Vlan bridge settings. →Upgrade to 3.8.0.1 |
1721 | 3.4.0.1 | 3.8.0.1 |
Wireless mesh mode is not compatible with DFS. Add check in the wireless settings →Upgrade to 3.8.0.1 |
1727 | 3.0.0.1 | 3.10.0.1 |
If the GRE local IP is not reachable when the GRE is initialized, all GRE traffic are send to the gateway. →Upgrade to 3.10.0.1 |
1768 | 3.6.0.1 | 3.8.0.1 |
In setup/physical interfaces overview, one error occur if the user select several channels in interface settings. →Upgrade to 3.8.0.1 |
1774 | 3.6.0.1 | 3.8.0.1 |
The MCS list is not generated on RailBox/21 and RailBox/25 →Upgrade to 3.8.0.1 |
1787 | 3.6.0.1 | 3.8.0.1 |
If the user change the product time zone, the product stay in UTC time zone. →Upgrade to 3.8.0.1 |
1826 | 3.6.0.1 | 3.10.0.1 |
In some cases the SRCC association can failed or is slow. →Upgrade to 3.10.0.1 |
1841 | 3.8.0.1 | 3.10.0.1 |
On Wln platform, the graphical bandwidth report doesn't work. →Upgrade to 3.10.0.1 |
1846 | 3.8.0.1 | 3.10.0.1 |
If the 802.11w is enable on the AP, it is doesn't work correctly. →Upgrade to 3.10.0.1 |
1856 | 3.8.0.1 | 3.10.0.1 | In setup/physique interface page the filters group link doesn't work. |
1863 | 3.6.0.1 | 3.10.0.1 |
The timezone settings is not correctly applied. →Upgrade to 3.10.0.1 |
1875 | 3.6.0.1 | 3.10.0.1 | The access to the page status wirless is not possible if all wireless card are disabled |
1887 | 3.8.0.1 | 3.10.0.1 |
With chrome version 55 some web page are not showed corretly. →Upgrade to 3.10.0.1 |
1910 | 3.10.0.1 | 3.10.1.1 |
The mesh SAE security don't work correctly with another WaveOS version. →Upgrade to 3.10.1.1 |
1911 | 3.10.0.1 | 3.10.1.1 |
It is not possible to create an VLAN Virtual interface on Wifi interface on mesh. →Upgrade to 3.10.1.1 |
1946 | 3.10.0.1 | 3.10.2.1 |
If you use SRCC on wifi 1 and AP on wifi 2, on certainly case the AP on wifi 2 can be disable during the SRCC association. →Upgrade to 3.10.2.1 |
1948 | 3.11.0.5 | 3.11.0.51 |
snmpd: fix engineID management
→Upgrade to 3.11.0.51 |
1951 | 3.10.0.1 | 3.12.0.1 |
In the web server, when the site survey is finished, in certainly case we don't see the result but we are redirected to the home page.
→Upgrade to 3.12.0.1 |
1955 | 3.11.0.1 | 3.14.0.1 |
It is not possible to change the Radius port in WPA/WPA2 settings.
→Upgrade to 3.14.0.1 |
1963 | 3.11.0.5 | 3.11.0.51 |
Fix snmpd agent version v3 value
→Upgrade to 3.11.0.51 |
1992 | 3.10.0.1 | 3.12.0.1 |
When the product is upgraded with NDM, the upgrade result from the product is "saving config files".
→Upgrade to 3.12.0.1 |
1996 | 3.10.0.1 | 3.12.0.1 |
In certanly case, the product can crash after several VRRP switch over.
→Upgrade to 3.12.0.1 |
2005 | 3.10.0.1 | 3.12.0.1 |
When the VRRP logs are enabled, some time the product can crash.
→Upgrade to 3.12.0.1 |
2007 | 3.10.0.1 | 3.12.0.1 |
In multicast routing, if the query interval is set to a value higher than 46s, the multicast routing can stop randomly.
→Upgrade to 3.12.0.1 |
2012 | 3.12.0.1 | 3.12.2.1 |
Fix system hanging during boot in some rare conditions.
→Upgrade to 3.12.2.1 |
2023 | 3.12.0.1 | 3.12.2.1 |
Fix antennas choice list.
→Upgrade to 3.12.2.1 |
2031 | 3.12.0.1 | 3.12.2.1 |
Certain advanced mesh parameters are not working properly.
→Upgrade to 3.12.2.1 |
2036 | 3.12.0.1 | 3.12.2.1 |
5GHz channels must not be usable in Israel.
→Upgrade to 3.12.2.1 |
2042 | 3.12.0.1 | 3.12.2.1 |
Can not configure bridge broadcast filter per snmp.
→Upgrade to 3.12.2.1 |
2044 | 3.12.0.1 | 3.12.2.1 |
Bridge filter is not working.
→Upgrade to 3.12.2.1 |
2045 | 3.12.0.1 | 3.12.2.1 |
Bridge filter rules are not applied on Ethernet port after a reboot.
→Upgrade to 3.12.2.1 |
2046 | 3.12.0.1 | 3.12.2.1 |
Error when displaying traffic class prio status page.
→Upgrade to 3.12.2.1 |
2047 | 3.12.0.1 | 3.12.2.1 |
SSIDs of wifi interfaces are not displayed in QOS traffic class prio submenu.
→Upgrade to 3.12.2.1 |
2049 | 3.12.0.1 | 3.12.3.1 |
In SRCC, the link establishement can be too long.
→Upgrade to 3.12.3.1 |
2051 | 3.12.0.1 | 3.12.3.1 |
In certainly case the discover service response can be not correct. The NDM view can be affected.
→Upgrade to 3.12.3.1 |
2056 | 3.12.0.1 | 3.12.3.1 |
If the bridge VLAN feature is enable and all bridge ports don't participate to the sames VLAN, some communication can not work correctly. This bug only affect the RailBox products.
→Upgrade to 3.12.3.1 |
2057 | 3.12.0.1 | 3.12.3.1 |
The bridge filter configuration through SNMP, can return some default values. These values are not writen in the configuration file. →Upgrade to 3.12.3.1 |
2058 | 3.12.0.1 | 3.14.0.1 |
Somes OID return the default value even if the value was not set.
→Upgrade to 3.14.0.1 |
2086 | 3.12.3.1 | 3.12.4.1 |
In certainly case it is not possible to set the client mode throught the Web interface. The interface return an error during the save process. →Upgrade to 3.12.4.1 |
2087 | 3.12.3.1 | 3.12.4.1 |
A buffer overflow can occure in Acksys Mib library. The result is some no consistant information is returned by the SNMP interface. →Upgrade to 3.12.4.1 |
2061 | 3.12.4.1 | 3.12.6.1 |
Roaming improvement with multiple Vlans topology →Upgrade to 3.12.6.1 |
2096 | 3.12.4.1 | 3.12.6.1 |
Reduction of packet loss during roaming →Upgrade to 3.12.6.1 |
2098 | 3.12.4.1 | 3.12.6.1 |
Enable routing in L25NAT mode with local router →Upgrade to 3.12.6.1 |
2109 | 3.12.4.1 | 3.12.6.1 |
Fix wrong status showed in NDM during roaming →Upgrade to 3.12.6.1 |
2112 | 3.12.4.1 | 3.12.6.1 |
Roaming: Add parameter to control station deauthentication →Upgrade to 3.12.6.1 |
2063 | 3.12.6.1 | 3.12.7.1 |
Reduction of packet loss on highest WMM QOS in case of network congestion →Upgrade to 3.12.7.1 |
2097 | 3.12.6.1 | 3.12.7.1 |
Fix: VRRP stops sending advertisements on an interface after that it has roamed. →Upgrade to 3.12.7.1 |
2116 | 3.12.6.1 | 3.12.7.1 |
VRRP: Fix initialisation issue →Upgrade to 3.12.7.1 |
2095 | 3.12.2.1 | 3.12.8.1 |
Multicast stream doesn't resume after the VRRP master reboot. →Upgrade to 3.12.8.1 |
2141 | 3.12.5.1 | 3.12.8.1 | The product ID used by NDM/WaveManeger is stored on configuration file and restored during the restore configuration process. If you restore a configuration on a product from another product, NDM, WaveManager will consider the both product as the same product. →Upgrade to 3.12.8.1 |
2144 | 3.12.7.1 | 3.12.8.1 |
Firewall rules without src and dest zone are not displayed in the web interface. →Upgrade to 3.12.8.1 |
2150 | 3.12.5.1 | 3.12.8.1 |
If network loop occure between the product network interface, an kernel crash occurs. →Upgrade to 3.12.8.1 |
2151 | 3.12.0.1 | 3.12.8.1 |
Wifi regulation domain: The chile was changed the regulation rule. Update the regulation domain to respect the new rules. →WARNING: This upgrade will reduce the Txpower to 17dBm on band 5735 - 5835 MHz. |
2154 | 3.12.0.1 | 3.12.8.1 |
SNMP: Fix some OID to allow router configuration. →Upgrade to 3.12.8.1 |
2156 | 3.12.0.1 | 3.12.11.1 |
SRCC: If the user select a chanel not compatible with the HT40+ mode, SRCC doesn't work →Upgrade to 3.12.11.1 |
2161 | 3.12.5.1 | 3.12.9.1 |
The mono-card repeater doesn't work.
→Upgrade to 3.12.9.1 |
2164 | 3.12.5.1 | 3.12.9.1 |
VRRP and static route: If the product have a static route and ip alias, after two VRRP transition (the product back in backup) static route is not correctly set and it is not possible to access at the product from far network.
→Upgrade to 3.12.9.1 |
2165 | 3.12.7.1 | 3.12.9.1 |
The roaming log level doesn't show the roaming log.
→Upgrade to 3.12.9.1 |
2182 | 3.10.0.1 | 3.12.9.1 |
We can set an IP address with an invalide format wihtout Error in the web page. eg: 192.168.010.20 is invalide because the digit '010' is an octal représentation and it is not supported by the firmware. →Upgrade to 3.12.9.1 |
2183 | 3.12.0.1 | 3.12.9.1 |
In NAT router configuration, some frames can be sent with the ip source set to an private IP.
→Upgrade to 3.12.9.1 |
2189 | 3.12.0.1 | 3.12.9.1 |
The bridge filter rules are not correctly applied on Wifi interface in AP mode configured to use a DFS channel.
→Upgrade to 3.12.9.1 |
2209 | 3.12.0.1 | 3.12.1.1 |
In snmp statusIfWlanTable, each wlan is present two times.
→Upgrade to 3.12.10.1 |
2210 | 3.10.0.1 | 3.12.10.1 |
The association counter (statusIfWlanPeers) don't work in mesh node.
→Upgrade to 3.12.10.1 |
2212 | 3.12.9.1 | 3.12.10.1 |
If two vrrp instance are configured in the same network, only one IP is applied.
→Upgrade to 3.12.10.1 |
2218 | 3.12.9.1 | 3.12.11.1 |
On EmbedAir and Airlink the WPA and WEP doesn't work.
→Upgrade to 3.12.11.1 or use WPA2 |
2220 | 3.10.0.1 | 3.12.10.1 |
In rarely case, the snmp deamon management can generate a configuration corruption.
→Upgrade to 3.12.10.1 |
2226 | 3.12.7.1 | 3.12.11.1 |
Fix product hanging in power save mode.
→Upgrade to 3.12.11.1 |
2234 | 3.12.9.1 | 3.14.0.1 |
The OID statusIpSubnetMenber from statusIpSubnetTable doesn't not give the list of interface member.
→Upgrade to 3.14.0.1 |
2235 | 3.12.9.1 | 3.12.11.1 |
The AP default settings are not the same in SNMP and Web interface
→Upgrade to 3.12.11.1 or change the values after the AP is added with the SNMP interface. |
2250 | 3.12.11.1 | 3.12.12.1 |
The status network web page doesn't work (error 500) if one wifi card is disabled.
→Upgrade to 3.12.12.1 or enable all wifi cards on the product. |
2254 | 3.12.11.1 | 3.12.12.1 |
The multicast routing deamon doens't work correctly when several IP address are set on managed interface.
→Upgrade to 3.12.12.1. |
2255 | 3.12.11.1 | 3.12.12.1 |
The firewall and VRRP configuration files are not well synchronised with network configuration file.
→Upgrade to 3.12.12.1. |
2273 | 3.10.0.1 | 3.12.12.1 |
The wireless status files can be corrupted.
→Upgrade to 3.12.12.1 or reset to factory the settings. |
2275 | 3.12.11.1 | 3.12.12.1 |
The VRRP deamon is not properly stopped when the configuration is reloaded.
→Upgrade to 3.12.12.1. |
2311 | 3.12.11.1 | 3.12.13.1 |
In WiFi client mode, If we received a Deauthentication frame from the AP the client will black list tis AP. In certainly case this list is not purged and the APs is not available for new association.
→Upgrade to 3.12.13.1. |
2321 | 3.12.11.1 | 3.12.13.1 |
The Atheros Adaptive noise imunity doesn't work correctly. This fix can increase the Wifi performance in case of noisy environment.
→Upgrade to 3.12.13.1. |
2318 | 3.12.12.1 | 3.14.0.1 |
The NTP client mays send the request before the interface is ready to forward the data. In this case the time synchronisation will perform on the next update.
→Upgrade to 3.14.0.1 |
2319 | 3.12.12.1 | 3.12.14.1 |
In WiFi roaming client mode, a wrong RSSI is sometimes obtained
from the Access Points which use a DFS channel. This may result
in incorrect selection of the Best AP to roam to.
→Upgrade to 3.12.14.1 or, →Reduce the beacon interval on all relevant AP's to less than 70 ms (or 70 TU) |
2343 | 3.12.11.1 | 3.14.0.1 |
The page status/wireless/assoc in web server may not display
→Upgrade to 3.14.0.1. |
2359 | 3.14.0.1 | 3.14.1.1 |
The web page to show the statistic graph show error and crash on wifi interface.
→Upgrade to 3.14.1.1. |
2369 | 3.14.0.1 | 3.14.1.1 |
On the EmbedAir1000 it is not possible to configure an AP in 802.11ac mode.
→Upgrade to 3.14.1.1. |
2371 | 3.14.0.1 | 3.14.1.1 |
In certainly case the signal level in client scan result is egal to 0.
→Upgrade to 3.14.1.1. |
2379 | 3.12.10.1 | 3.14.1.1 |
In SRCC configuration, if the link is broken, it will be never restablished.
→Upgrade to 3.14.1.1. |
2389 | 3.14.0.1 | 3.14.1.1 |
In system log if the line is too long that can store a line with some garbage.
→Upgrade to 3.14.1.1. |
2390 | 3.12.13.1 | 3.14.1.1 |
If we configure an AP with pre-authentication in some case this feature is not enabled on the AP.
→Upgrade to 3.14.1.1. |
2391 | 3.14.0.1 | 3.14.1.1 |
in mono-channel roaming configuration, the foreground scan doesn't work properly.
→Upgrade to 3.14.1.1. |
2399 | 3.14.0.1 | 3.14.1.1 |
On RaiBox/RailTrack Ethernet interface Transmit fifo can overflow and occurs some packet lost.
→Upgrade to 3.14.1.1. |
2403 | 3.10.0.1 | 3.14.1.1 |
In case of the configuration is restored from the C-KEY after an reset to factory settings, the network configuration stay in default settings.
→Upgrade to 3.14.1.1. |
2409 | 3.12.7.1 | 3.14.2.1 |
If the product is set in DHCP mode, in Wifi client mode and bridging mode in ARPNAT, the product will reboot each time it should renew the DHCP lease.
→Upgrade to 3.14.2.1 or use the WDS bridging mode (not compatible with roaming). |
2413 | 3.14.0.1 | 3.14.2.1 |
The status page status/wireless/services_status will generate an error in syslog.
→Upgrade to 3.14.2.1. |
2416 | 3.14.0.1 | 3.14.2.1 |
If the product is set in DHCP mode, in Wifi client mode and bridging mode in ARPNAT, the checksum is wrong in the first renew frame sent. The renew at half lease dont' work properly.
→Upgrade to 3.14.2.1. |
2417 | 3.14.1.1 | 3.14.2.1 |
The factory settingss on RailBox is wrong. The ip address is set to 192.168.1.1 and only LAN1 is in the default bridge.
→Upgrade to 3.14.2.1 and reset the settings or make a new configuration. |
2423 | 3.14.0.1 | 3.14.3.1 |
If the profinet cloning is configured on the radio1, the system create the interface on the radio0.
→Upgrade to 3.14.3.1. |
2425 | 3.16.0.1 | 3.16.1.1 |
The pin code is sent 2 time during the init.
→Upgrade to 3.16.1.1. |
2427 | 3.14.0.1 | 3.14.3.1 |
The NTP client can have a synchronisation issue at startup.
→Upgrade to 3.14.3.1. |
2428 | 3.14.0.1 | 3.14.3.1 |
On AirLink, EmbedAir the time zone is not configured correctly.
→Upgrade to 3.14.3.1. |
2443 | 3.14.0.1 | 3.14.3.1 |
In some case the PIM deamon coud not start correctly.
→Upgrade to 3.14.3.1. |
2444 | 3.14.0.1 | 3.14.3.1 |
Update the wifi regulation domain for Qatar country.
→Upgrade to 3.14.3.1. |
2446 | 3.16.0.1 | 3.16.1.1 |
The LTE/GNSS daemon crash if it use an empty sim slot.
→Upgrade to 3.16.1.1. |
2448 | 3.16.0.1 | 3.18.0.1 |
When the GNSS is fixed, the date returned throught the snmp interface is always the same.
→Upgrade to 3.18.0.1. |
2464 | 3.16.0.1 | 3.18.1.1 |
The user's default netmask in openvpn settings is not saved.
→Set the user's default netmask or upgrade to 3.18.0.1. |
2466 | 3.16.0.1 | 3.18.1.1 |
The openvpn settings doesn't work with NAT configuration.
→Upgrade to 3.18.0.1. |
2470 | 3.16.1.1 | 3.18.1.1 |
In the QOS tagging feature, the destination IP field of the rule is ignored.
→Upgrade to 3.18.0.1. |
2472 | 3.14.3.1 | 3.14.5.1 |
In roaming case, if we didn't receive a probe response from the AP we will send a probe to the AP before the association.
The association is make after a probe response timeout (200ms).
this case occur on each roaming if we use a DFS channel.
→Upgrade to 3.14.5.1. |
2474 | 3.14.3.1 | 3.14.5.1 |
The 802.11r feature is not enabled correctly.
→Upgrade to 3.14.5.1. |
2486 | 3.14.3.1 | 3.14.5.1 |
In some case, on product with 2 or more WiFi cards, the regulatory domain can be not set properly.
→Upgrade to 3.14.5.1. |
2488 | 3.14.3.1 | 3.14.5.1 |
It is not possible to set the log level when 2 or more AP were configured on the same WiFi card.
→Upgrade to 3.14.5.1. |
2501 | 3.16.1.1 | 3.18.0.1 |
The IMSI/IMEI are not show if the LTE module is not connected.
→Upgrade to 3.18.0.1. |
2503 | 3.16.1.1 | 3.18.0.1 |
The event settings web page show an error on the AirBox.
→Upgrade to 3.18.0.1. |
2532 | 3.14.5.1 | 3.18.0.1 |
It is not possible to configure an AirLink V2 with the configuration file from AirLink V1.
→Upgrade to 3.18.0.1. |
2544 | 3.14.5.1 | 3.18.0.1 |
it is possible to lost some configuration information on AirLink, EmbedAir, AirBox, RuggedAir, AirXroad.
→Upgrade to 3.18.0.1. |
2560 | 3.14.5.1 | 3.18.0.1 |
The PIM-SM protocol is not enable in the kernel. The multicast routing does not work on AirLink, EmbedAir, AirBox, RuggedAir, AirXroad.
→Upgrade to 3.18.0.1. |
2560 | 3.14.5.1 | 3.18.0.1 |
It is not possible to use a non RSA private key.
→Upgrade to 3.18.0.1. |
2574 | 3.15.5.1 | 3.18.1.1 |
On Airlink, RuggedAir, EmbedAir1000, AirBox, it is not possible to use the Ethernet interface with a link negotiated at 10 Mbps HD.
→Upgrade to 3.18.1.1. |
2575 | 3.18.0.1 | 3.18.1.1 |
If we configure 2 roles on the same Wi-Fi radio, the status in status->network is wrong.
→Upgrade to 3.18.1.1. |
2581 | 3.18.0.1 | 3.18.1.1 |
on AirBox, it is not possible to configure an event on the second digital output.
→Upgrade to 3.18.1.1. |
2584 | 3.14.5.1 | 3.14.6.1, >3.18.1.1 |
Wi-Fi client roaming option "Do not cache old scan results" has not effect in radio cluster mode.
→Upgrade to fixed version. |
2613 | 3.14.5.1 | 3.14.7.1 |
In some case, GRE interface is destroyed and multicast routing fails.
→Upgrade to 3.14.7.1 |
2663 | 3.14.6.1 | 3.18.2.1 |
If the network settings were changed, and the save and apply command is sent from SNMP interface, the SNMP deamon hang.
After this action, it is not possible to reach the product through the SNMP interface.
→Upgrade to 3.18.2.1 |
2666 | 3.18.1.1 | 4.4.0.1 |
In some case, if the AP is configured in HT40 it can work in HT20.
→Upgrade to 4.4.0.1 |
2684 | 3.18.2.1 | 3.18.3.1 |
In some cases (dependent on the configuration files) when an application read the OID ConfigIpSubnet the snmp deamon crash.
→Upgrade to 3.18.3.1 |
2731 | 3.14.1.1 | 4.2.0.1 |
the snmp scan with the OID .1.3.6.1.4.1.28097.7.4 doesn't work correctly
→Upgrade to 4.2.0.1 |
2776 | 3.14.1.1 | 4.2.0.1 |
The default log level is set to "no log" for wifi deamons. This level does not allow to show the basic connection errors. Set the default log level to "info" for sta deamon.
→Upgrade to 4.2.0.1 |
2814 | 4.0.0.1 | 4.4.0.1 |
SRCC doesn't work
→Upgrade to 4.4.0.1 |
2818 | 3.18.3.1 | 3.18.4.1 4.2.0.1 |
If the engineID is set to motherboard ID, the engine ID is still the same on all products.
→Upgrade to 3.18.4.1 or 4.2.0.1 and reselect the option. |
2825 | 3.14.6.1 | 4.2.0.1 |
In the roaming with cluster mode scan, the product may reboot.
→Upgrade to 4.2.0.1 |
2833 | 3.18.3.1 | 4.2.0.1 |
If the ntp server is not reachable for 60s, the ntpclient service is stopped.
→Upgrade to 4.2.0.1 |
2842 | 4.0.0.1 |
MESH mode doesn't work
→upgrade to 4.8.0.1 | |
2854 | 4.2.0.1 | 4.2.1.1 |
On DFS channels, detection of some short pulses from radars fails.
→Upgrade to 4.2.1.1 |
2864 | 4.2.0.1 | 4.2.1.1 |
On DFS channels, radars detection brings up many false positives, resulting in
the Access Point service going to the "DFS-NOP" state (visible in the web interface).
→Upgrade to 4.2.1.1 |
2875 | 4.2.0.1 | 4.4.0.1 |
If the user password is wrong, the web interface shows an error message.
→Upgrade to 4.4.0.1 |
2878 | 4.2.0.1 | 4.4.0.1 |
The time to read some OID is very long.
→Upgrade to 4.4.0.1 |
2885 | 4.0.0.1 | 4.4.0.1 |
in roaming condition, the scan frames are not always sent. This result in an incomplete scan result.
→Upgrade to 4.4.0.1 |
2889 | 4.0.0.1 | 4.4.0.1 |
in roaming condition, if a large bandwith is sent in the QOS level VO, the client disconnects.
→Upgrade to 4.4.0.1 |
2938 | 4.4.0.1 | 4.4.1.1 |
Parameters "Maximum time above maximum level" and "Maximum time under minimum level" are no longer visible in the WEB interface (but if they were defined before upgrade to 4.4.0.1, they remain valid). The correction makes them visible again.
→Upgrade to 4.4.1.1 |
2939 | 4.4.0.1 | 4.8.0.1 |
In client mode (without roaming) if you select several channels, the client still scan all channels.
→Upgrade to 4.8.0.1 |
2943 | 4.4.0.1 | 4.4.1.1 |
If the WiFi interface is not selected in the network named "LAN", it is not possible to set the LAN network IP via WaveManager.
→Upgrade to 4.4.1.1 |
2996 | 4.4.0.1 | 4.8.0.1 |
The GPS coordinates are not accurate from SNMP interface
→Upgrade to 4.8.0.1 |
2999 | 4.4.1.1 | 4.4.2.1 |
The setup->physical interface web page is not displayed correctly. An error prevents the Wi-Fi configuration.
→Upgrade to 4.4.2.1 |
3007 | 4.4.0.1 | 4.4.3.1 |
The dhcp Server may not start after a reboot, or may be stopped soon after.
→Upgrade to 4.4.3.1 |
3015 | 4.4.3.1 | 4.4.4.1 |
Sometimes the network service does not work at product startup.
→Upgrade to 4.4.4.1 |
3017 | 4.4.4.1 | 4.4.5.1 |
In some cases, the web page to configure the cellular return an error 500.
→Upgrade to 4.4.5.1 |
3018 | 4.4.4.1 | 4.8.0.1 |
In some cases, in the web interface, it is not possible to add firewall zone.
→Upgrade to 4.8.0.1 |
3050 | 4.4.0.1 | 4.4.5.1 |
The SNMP service stops working if the cellular interface is enabled and no SIM card is present.
→Upgrade to 4.4.5.1 |
3051 | 4.4.0.1 | 4.4.5.1 |
From SNMP interface, the IP configuration for cellular interface is always set to none.
→Upgrade to 4.4.5.1 |
3070 | 4.4.0.1 | 4.10.0.1 |
When a static route it use with the VPN service, the static routes are not applied in all cases.
→Upgrade to 4.10.0.1 |
3072 | 4.4.0.1 | 4.8.0.1 |
In SNMP interface, The oid ifIndex of the table statusIPSubnetTable can return a random value if the interface is down.
→Upgrade to 4.8.0.1 |
3084 | 3.18.3.1 | 4.4.5.1 |
On cellular product, it's impossible to use SIM 2.
→Upgrade to 4.4.5.1 |
3085 | 3.18.3.1 | 4.4.5.1 |
Error message in the cellular upgrade web page.
→Upgrade to 4.4.5.1 |
3090 | 4.4.4.1 | 4.4.5.1 |
If the product is configured as DHCP client, and the DHCP server doesn't send NTP server information in the lease, the NTP setting in the product is lost.
→Upgrade to 4.4.5.1 |
3093 | 4.4.4.1 | 4.4.5.1 |
For some countries, it is not possible to configure the 802.11 mode.
→Upgrade to 4.4.5.1 |
3094 | 4.0.0.1 | 4.8.0.1 |
The cloning feature (profinet or wired) doesn't work.
→Upgrade to 4.8.0.1 |
3097 | 4.0.0.1 | 4.8.0.1 |
If the Wi-Fi interface is bridged to another interface and configured to use the '4 addr format (wds)', the WPA/WPA2-EAP security policy doesn't work. The authentication is not possible.
→Upgrade to 4.8.0.1 |
3099 | 4.0.0.1 | 4.8.0.1 |
The identity parameter is required for EAP-TLS authentication. For compatibility reason, the identity 'Acksys' is used if the parameter is not set.
→Upgrade to 4.8.0.1 |
3105 | 4.8.0.1 | 4.10.0.1 |
In cluster mode "group for scanning", The scan duration for DFS channel is more important then the version 3.
→Upgrade to 4.10.0.1 |
3123 | 4.8.0.1 | 4.8.1.1 |
The USB clock is not configured correctly on the Railbox. At boot time, the cellular card can be not detected.
→Upgrade to 4.8.1.1 |
3230 | 4.8.0.1 | 4.8.1.1 |
At startup, if the cellular card is not detected, the cellular configuration is cleared.
→Upgrade to 4.8.1.1 |
3195 | 4.10.0.1 | 3.18.3.1 |
In AP mode, after a DFS event the AP is configured as isolated AP.
→Upgrade to 4.10.0.1 |
3202 | 4.8.0.1 | 4.10.0.1 |
After a reset to factory settings, the web page Status/Wireless show an error.
→Upgrade to 4.10.0.1 or reboot the product |
3216 | 4.8.0.1 | 4.10.0.1 |
The web Page wireless/survey allow a script injection by the URL. That can allow to execute malicious code.
→Upgrade to 4.10.0.1 |
3245 | 4.8.0.1 | 4.10.0.1 |
In Alarm/event feature, the pinger event doesn't work correctly.
→Upgrade to 4.10.0.1 |
3248 | 4.8.0.1 | 4.10.0.1 |
The system cron log can be not properly applied.
→Upgrade to 4.10.0.1 |
3232 | 3.18.0.1 | 4.10.0.1 |
When a cloning mode is enabled on the wifi interface, sometimes, after cloning the signal level is not correct and the wifi client cannot associate with the AP.
→Upgrade to 4.10.0.1 |
3264 | 4.8.0.1 | 4.10.1.1 |
It is not possible to load an AirBox V1 configuration file in the AirBox V2 product.
→Upgrade to 4.10.1.1 |
3275 | 4.8.0.1 | 4.10.1.1 |
On 11ac wifi cards, if only the antenna 1 is set, the wifi services doesn't work properly.
→Upgrade to 4.10.1.1 |
3396 | 4.10.0.1 | 4.10.1.1 |
In some cases, the products may revert to default settings after power cycling. →Impacted product: AirLink, AirBox, RuggedAir, EmbedAir, AirXroad, WaveNet-EX →Upgrade to 4.10.1.1 |
3406 | 4.10.0.1 | 4.12.0.1 |
WEP security can be set, but this security mode is not supported by driver.
→Upgrade to 4.12.0.1 |
3410 | 4.10.0.1 | 4.12.0.1 |
The OIDs under lanInterface doesn't work correctly.
→Upgrade to 4.12.0.1 or use the OIDs under networkConfiguration and networkStatus |
3419 | 4.10.0.1 | 4.12.1.1 |
The spectral analyzer from the WEB interface doesn't work (Site Survey).
→Upgrade to 4.12.1.1 |
3423 | 4.8.0.1 | 4.12.1.1 | In rare cases, when wifi roaming is enabled, it may take a long time to recover the WiFi link after a communication error with the new AP. To prevent any hardware failure an optional watchdog has been added. |
3431 | 4.10.0.1 | 4.12.1.1 | If a client roam between Acksys APs, the communication can stop. →Impacted product: RuggedAir1000, Airbox |
3437 | 4.12.0.1 | 4.12.1.1 | When the VRRP service is enabled, it does not notify other VRRP routers when it needs to shut down (to apply settings or to reboot the product). |
3457 | 4.8.0.1 | 4.12.1.1 | If the network IP scheme in the network is not compatible with the RFC1918, some access problem to the builtin WEB server may happen. |
3463 | 4.12.0.1 | 4.12.2.1 | If you define an 802.1q virtual interface with VLAN ID equal to 1, in some cases adding a new 802.1q virtual interface may change the configuration of other 802.1q virtual interfaces already present. |
3475 | 4.10.0.1 | 4.12.2.1 | From the site survey, it is not possible to join an AP with WPA3 security. |
3444 | 4.10.0.1 | 4.12.2.1 | The WPA3 status is not correct from SNMP. WaveManager is not able to show correctly the WPA3 settings, and in the site survey from the WEB interface, the security mode is not correct. |
3472 | 4.10.0.1 | 4.12.2.1 | The VLAN priority is not correctly handled on the WiFi interfaces. All frames are sent with the BE policy regardless of the frame priority. |
3476 | 4.10.0.1 | 4.12.2.1 | In the Site Survey from SNMP interface, the WPA3 security mode is not correctly handled. The security mode shown is not correct. |