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
Release Date: 2016.08.01
Revision 1.0: 2016.08.01

New Features
1. Add support for the L7571 Platform.
2. Firmware supports the Edge Appliances.
3. The Edge products are able to control the system fan via a smart fan system.

1. Ethernet port Interrupt Throttle Rate will be configurable for legacy hardware types.
2. Added the ability to specify a source WAN when using diagnostics traceroute via the CLI.

1. All Powerlink devices will have access to the firewall and the VPN features.
2. Remove maximum global limit of 64 LANs.
3. The GUI will accept both CIDR and Dotted Decimal notations for IP Network Address fields.
4. Add configurable default WAN Test Points.

1. A WAN Virtualization site which has at least 1 dynamic site configured and a static site configured will not allow the dynamic tunnels to establish.
2. WAN Virtualization static routes may not work properly if dynamic WAN's are used and the dynamic IP address changes.
3. Encrypted WAN Virtualization sites that use dynamic WAN's can allow unencrypted traffic to flow if the VPN goes down after a dynamic WAN IP address changes.
4. An Encrypted WAN Virtualization site which contains dynamic tunnels can get into a state where the dynamic tunnels stop passing traffic. This can occur if the local dynamic WAN IP address changes. NOTE: If the dynamic site is experiencing this issue then both the sites using the WAN Virtualization feature should be on the newer version.
5. Making alias changes may cause the device software to restart.
6. WAN entries can show incorrect status if an individual test takes more time than specified.
7. Compression option will be removed from the WAN Virtualization feature.
8. Attempting to activate on a DNS domain page can fail when it is associated to a reverse zone.
9. Making VPN configuration changes can cause device software to restart.
10. The VoIP feature may not become enabled after disabling then re-enabling it.
11. WAN Virtualization will send email alerts for tunnel bounces only after a configurable number of bounces in a time period.
12. Modify memory parameters used to trigger alerts to avoid false alerting.
13. Telnet option removed from user interface since it is no longer supported.
14. A WAN which is configured to be DHCP can show the mask as /0 instead of the correct mask when a DHCP address is received.
15. Adding or modifying a WAN in the GUI, and leaving Test IP addresses blank, results in incorrect WAN recovery testing.
16. Ecessa VoIP authentication configuration with user names that contain special characters can cause the configuration to not load.
17. A configuration where a spare WAN is before another WAN can cause the other WAN to not change state when it goes down.
18. Importing a VoIP Authentication domain can fail when the entries contain comma characters.
19. Port forwarding feature in the Web GUI does not accept the keyword "Any" for a port range.
20. VoIP authentication domains that are configured with the line name or the password containing an apostrophe can cause the domain page to not show all the entries after activation.
21. Deleting a wan peer from a bridged WAN deletes the peer-to-peer IP address from the WAN port.
22. The CLI 'firewall show' command prints out an empty source if not set.
23. A WAN peer for the gateway added to a translucent WAN can cause WAN testing to fail and the WAN to go down.
24. VoIP call failover can take a long time due to support for silence suppression.
25. Add an option to prevent clickjacking attacks on the web interface.
26. After creating a bridge in the CLI you can not use the bridge alias as a port when creating a WAN.
27. When a WAN Virtualization site comes up it is possible that the default route for the site does not contain all the tunnels that it should contain.
28. WAN Virtualization can incorrectly determine the health of a site and attempt to recover the site which causes all tunnels to be bounced.
29. Encrypted WAN Virtualization VPN connections can lose their ability to properly route traffic.

Known Issues
1. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN security association entry which has no name.
2. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
3. 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.
4. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
5. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
6. DNS Reverse Zone may not work correctly for load-balanced hosts.
7. 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.
8. Activating Port Forwarding configuration changes can cause the device software to restart.
9. WAN Virtualization hub location cannot have a site number that is greater than 127.
10. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected.
11. IPSec VPN Failback option does not work as expected.
12. When changing static routes that use aliases it is possibie that traffic could continue using the WAN over which it was previously routed.
13. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.

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


Please sign in to leave a comment.