February 2024 Appliance Release Notes

Removal of Local UI System

The local UI functionality allowed users with direct physical access to an appliance network port to connect to a lightweight web server on the appliance to change the WAN interface IP and see the connectivity status. Several years ago, this solution was augmented with the Console Utility which has proved easier to use and has been expanded to provide much more functionality. The local UI has now been removed to simplify the appliance and focus efforts on the Console Utility.

VPN Sniff Improvements

This release improves the Virtual Network Sniff tool to allow more flexibility matching based on ports. We now support port matching based on:

• equal (=)
• not equal (!=) to exclude traffic for the specified port
• greater than (>) and less than (<)
• a port range (<>) which will show all traffic with ports between the two values

  

Agent Support

Gateways running this version will be the first to support the new lightweight Trustgrid agent-based nodes. More details will be announced once the agent has been officially released.

Other Improvements

• The JVM Heap metric is now exposed via the Trustgrid SNMP OID
• The dig and nslookup commands are now available from the Console Network Tools Shell
• Remote Console Registration no longer forces upgrading to the latest version. This makes the process of registration quicker, though it is still recommended to upgrade to the latest version after the node is online.

Other Fixes

• Resolves where a null pointer exception in the code for tracking peer tunnel latency could cause a memory leak that would eventually lead to appliance instability and outage.
• If a BGP server received a route removal update, it would remove the OS route but sometimes not update the BGP table. Then if the same route was added back, the BGP server would fail to recreate the OS route. This release resolves this issue.
• Resolves an issue where traffic egressing a Virtual Network would not evaluate the specificity of interface routes when determining the next hop. For example, if you had two routes (172.16.22.0/24 and 172.16.22.100/32) with different next hops, the more specific /32 route next hop was not utilized.
• Resolves an issue with Access Policies using the reject action. The reject response (e.g. RESET for TCP) generated had the source and destination IPs transposed. This release fixes the source/destination IP placement in reject responses.
• Changed the default JVM allocation for Lanner NCA-1210, NCA-1513, NCA-1515 and NCA-1010 from 3G to 2G. This only impacts newly registered nodes.