June 2020 Release Notes

Tools Input Improvement

Trustgrid is working to make our tools more user friendly. Prior to this release when launching Troubleshooting Tools you were prompted to enter in additional parameter via a multiline text box such as below.

This input method could be difficult to deal with, especially when copying and pasting values. Therefore starting with this release our prompts use a form layout with individual fields for each parameter.


Virtual Routes Table Improvements

Similarly we have made improvements to one of the most commonly used VPN tools, View Virtual Routes Table.

First, launching this tool can now be performed via a button on the VPN panel of a Node.

And the output of the tool has been greatly improved from the old text display to a full HTML display as shown below.

This allowed us to make the additional improvements including:

  1. The route table can be quickly searched using the Search input or Advanced Search filter

  2. The destination device is now displayed as a clickable link to make it easy to jump to the page of that device.

  3. If the destination of a route is a cluster we display the current cluster master, also in the form of a link.

  4. We display the connectivity status of the destination of the device. A green, upward pointing arrow (or a green circle) indicates that the node you are currently viewing has an available route to the target device. A red, downward pointing arrow indicates the node cannot establish a connection to the target device.

Virtual Interface / VLAN Support

Finally, starting with node version 20200506 we are adding the ability to create virtual subinterface devices using standard VLAN tagging methods. This is currently only supported on dual interface devices and only on the LAN interfaces. It does require the connected switch port be configured to support whatever VLANs are used.

The basic process to setup is:

  1. Enable the LAN interface if it is not already and assign an IP address.

    1. Traffic on the physical interface will be untagged

    2. If no traffic is expected on the physical interface you will still need to provide an IP, even if not functional.

  2. From the Configuring dropdown select “New Subinterface”

  3. You will be prompted to provide:

    1. The VLAN ID to be used

    2. An IP address in CIDR notation.

  4. Further down you can define any additional routes this interface needs to access other networks and the Next Hop router IP for those networks.


  5. Click Save to commit the changes. The node service will add the new subinterface and IP information