Ecessa Firmware Release Notes
Release Date: 2019.03.18
Revision 1.0: 2019.03.18
1. Firmware update user interface updated to show more information about available versions.
1. WAN Virtualization sites using double digit site ID's can result in extra PPP connections staying around after tunnels bounce.
2. Some SSL clients running new software versions will not connect to SSL VPN due to weak message digest algorithm.
3. Virtual Product has a missing log file.
4. 'View Ecessa Mib' does not include the beginning section in the web interface.
5. A WAN Virtualization site can get in to a state where a tunnel appears to repeatedly come up and go back down but never actually connects.
6. Maximum number of sessions are not set correctly for PL1200 and PL4000 models.
1. Creating a WAN using the CLI, with an alias of 24 characters, causes a software restart.
2. Creating a WAN Virtualization site with a name longer than 22 characters causes a software restart.
3. Disabling WAN Virtualization, or a hardware failover occurring when WAN Virtualization is enabled, on a busy system can result in a software deadlock.
4. When a device is running a configuration which has WAN Virtualization sites and loads a configuration which does not have WAN Virtualization sites configured the device software may restart.
5. Virtual Product may boot slowly.
6. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
7. The DHCP service can stop unexpectedly.
8. The LCD display can become stuck and not display new information when keys are pressed.
9. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN entry with no name.
10. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
11. Using the CLI to create an alias with multiple addresses will reorder the addresses and remove duplicates, making the alias unusable for firewall forwarding rules.
12. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
13. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
14. DNS Reverse Zone may not work correctly for load-balanced hosts.
15. WAN Virtualization which is using non base IP addresses can not route as expected when a static route is in place which applies to all traffic.
16. WAN Virtualization hub location cannot have a site number that is greater than 127.
17. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
18. Failback static route over WAN Virtualization doesn't fail back after failing over to a WAN.
See Ecessa's full line of products and solutions