Ecessa Firmware Release Notes Version: 10.6.7 Release Date: 2017.01.16 Revision 1.0: 2017.01.16 Fixes 1. Static Routes with a destination of 0.0.0.0/0 do not get applied. 2. Port Link Speed and Duplex Settings can get stuck displaying 'Auto Negotiate' when there are manual settings selected. 3. When dynamic local endpoint for WAN Virtualization/Channel Bonding site is entered as an IP, the site will not function correctly. 4. DNS SOA e-mail entry is too strict which does not allow valid SOA e-mail addresses. 5. WAN Virtualization status is not correct when viewing the live site from the cloud. Known Issues 1. Virtual Product may boot slowly. 2. Adding an encrypted WAN Virtualization site using the CLI may not work as expected. 3. The DHCP service can stop unexpectedly. 4. The LCD display can become stuck and not display new information when keys are pressed. 5. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN security association entry which has no name. 6. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN. 7. 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. 8. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive. 9. Using Hardware Failover with high traffic throughput can cause excessive loading of the device. 10. DNS Reverse Zone may not work correctly for load-balanced hosts. 11. 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. 12. Activating Port Forwarding configuration changes can cause the device software to restart. 13. WAN Virtualization hub location cannot have a site number that is greater than 127. 14. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected. 15. IPSec VPN Failback option does not work as expected. 16. When changing static routes that use aliases it is possibie that traffic could continue using the WAN over which it was previously routed. 17. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow. 18. A VTI VPN on an Ecessa device which is behind NAT will not be able to connect.
Have more questions? Submit a request