Description6.4.6 Update 1
This release includes all changes from releases up to and including these update releases: 6.3.13, 6.4.1 Update 1, 6.4.2 Update 3, 6.4.3 Update 11 and 6.4.4, 6.4.5, 6.4.6
No 32-bit images are provided. 6.4 is not supported on 32-bit hardware.
Platforms: 2061, 3062, 4010, 4061, 4062, 6060, 6062, 8060, 8062, 10060, 10062, Virtual
Supported upgrade versions: 6.0, 6.1, 6.3, 6.4
Link to download:
64 bit image
File size: 415,957,590
Notices : If you are upgrading to ExOS 6.4 from ExOS 5.x or earlier, this upgrade is not supported. Please upgrade to ExOS 6.3 first.
New images for the Virtual appliances are not available. To install a new virtual appliance running 6.4.6, please first install 6.3.0 and upgrade to 6.4.6.
Updated Layer 7 signatures [B-04396]
¥Adobe Creativ Cloud
¥Ultrasurf: Set the correct real protocol when necessary, before Ultrasurf v14.03 was classified as SSL
Bug fixes and minor improvements:
6.4.6 Update 1 includes all fixes and changes up to and including 6.4.6.
[D-03733] Fixed an issue with Acceleration Clustering where during a fail over event, existing accelerated connections may stop working
[D-03172] Fixed an issue where the Hosts PDF report could show the wrong data for Internal hosts. The pie chart was correct but the corresponding table was showing External hosts.
[D-03772] Fixed an issue that when an acceleration HA cluster is configured and the traffic being accelerated is located on a VLAN and has a VLAN tag, the traffic will not flow through the HA cluster properly. Please note that Cluster interface MTU should be at least 1538 due to the addition of the VLAN protocol and TCI fields.
[D-03779] Fixed an issue where the VRRP Master would keep changing if two VRRP IDs were configured on a single appliance.
[D-03982] Fixed various ntp vulnerabilities
[D-03897] Fixed an issue where connections that hairpin at a "Network Orchestrator in the middle" would break if acceleration was enabled in all Network Orchestrator appliances. This situation is common when two branches are communicating through a central data centre. This issue only happened when the data centre had a cluster of appliances.