Welcome to Ecessa Support, we have a variety of technical information and tools for a variety of solutions. If you aren't finding a solution, or would like to talk to a technical support team member, please call 800-669-6242.

See Ecessa's full line of products and solutions

Ecessa Firmware Release Notes
Version: 11.0.0
Release Date: 2019.03.18
Revision 1.0: 2019.03.18

New Features
1. SSD drives support swap which allow part of the drive to be used for memory when system memory is not available.
2. Ability to capture device crash reports.

1. PPPoE WAN's will use a default MTU of 1452.
2. Add IPv6 support to the Ecessa SNMP MIB.
3. Ability to set Diffie-Hellman key size to be used for web server HTTPS.
4. Add support for DNS CAA records.
5. Allow DHCP Relay to be used when LAN DHCP servers are configured on the device as long as they use different LANs.

1. Add ability to configure Diffie Hellman key size for SSL VPN connections, either 1024 or the default 2048.
2. Firmware update user interface updated to show more information about available versions.
3. Devices with SSD drives now support multiple firmware versions on the device as well as a recovery firmware.

1. VPN non-legacy autostart does not work correctly in firmware 11.0.0+ after WAN changes are made.
2. WAN Virtualization sites using double digit site ID's can result in extra PPP connections staying around after tunnels bounce.
3. Some SSL clients running new software versions will not connect to SSL VPN due to weak message digest algorithm.
4. Virtual Product has a missing log file.
5. CLI diagnostics iperf will not initially connect over a site-to-site IPSec VPN connection.
6. VPN IPSec VTI connections now require wide open traffic selectors in order to allow routed traffic through.
7. Disabling WAN Virtualization, or a hardware failover occurring when WAN Virtualization is enabled, on a busy system can result in a software deadlock.
8. Registering a virtual machine with a group name that is more than 24 characters will report that the group does not exist even if it does.
9. WAN Virtualization static route tunnels were not being configured correctly using the CLI.
10. Authoritative DNS zone may load improperly on config load.
11. WAN Virtualization compression can cause traffic to be dropped when a tunnel bounces.
12. Clients which do not support 'comp-lzo' setting may be unable to connect to a SSL VPN.
13. 'View Ecessa Mib' does not include the beginning section in the web interface.
14. CLI command dns notify does not work.
15. 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.
16. Web links to statistics on QoS page go to the wrong page.
17. Maximum number of sessions are not set correctly for PL1200 and PL4000 models.

Known Issues
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. 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.
4. Virtual Product may boot slowly.
5. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
6. The DHCP service can stop unexpectedly.
7. The LCD display can become stuck and not display new information when keys are pressed.
8. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN entry with no name.
9. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
10. 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.
11. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
12. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
13. DNS Reverse Zone may not work correctly for load-balanced hosts.
14. 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.
15. WAN Virtualization hub location cannot have a site number that is greater than 127.
16. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
17. Failback static route over WAN Virtualization doesn't fail back after failing over to a WAN.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.