Release Notes 2.2.2

• Multiple Overlays
• Multiple Underlays
• Port Groups
• Network Objects
• Automatic policy creation based on user type
• Ability to change the LSI for regional compatibility
• Windows User auth MFA

• Cellular carrier connection issues
• Modbus GUI settings or connectivity
• HS-100 connectivity issues
• Use the 1.0.0.0/8 network address space
• Network capture on Conductor 500

Improved the route injection option to eliminate additional user actions. The new behavior is as follows:

Event Monitor of type HIP tunnel does not allow you to specify monitored peers.

Workaround: None

Currently, you cannot stop a packet capture once initiated from the Conductor UI for a macOS HIPclient.

Workaround: Wait for the packet capture operation to terminate.

When downgrading the HS-150 from 2.2.0 to 2.1.6, the cellular link LEDs may not be functional.

Workaround: In order to restore LED functionality, in Conductor, change the "Underlay network" settings under the "Ports" tab. For example, adjust the priority. (Note that you may need to provide the "Access point name (APN)" since that field may appear blank, in order to successfully apply the settings.) After applying the settings, reboot the HS-150 for the Cellular LEDs to become functional again.

If a HIPswitch is factory reset, its details may not be removed from the Conductor UI.

Workaround: none.

When downloading a support bundle, the dialog box contains two buttons, Download and Cancel. Cancel has the same effect as closing the dialog.

Workaround: None.

The HIPswitch 400 and HIPswitch 500 LCD menus do not support setting Conductor host names longer than 16 characters.

Workaround: Configure the corresponding IP address instead.

Currently, the hipsh console will not timeout and may become locked.

Workaround: Reboot or power-cycle the HIPswitch.

Once a HIPrelay learns an IPv4 / IPv6 address for a peer, it will continue to use that address indefinitely for forwarding peer packets). If the peer is offline and doesn't update its address with the HIPrelay, the old or invalid address will continue have HIP control packets forwarded to it.

Workaround: None

In rare cases, the Apply Firmware Updates dialog will show duplicate entries in the Upgrade Available drop-down.

Workaround: None.

Retransmitted HIP I1 packets are only sent using one source address/destination pair. This differs from the initial I1 packets which attempt to use all source/destination address combinations.

This issue occurs on multi-homed HIPswitches, with peer-auto connect turned on and relay probes off.

Workaround: None.

The tray application crashes repeatedly and prevents the configuration of the HIPclient or HIPserver.

Workaround: Reinstall .NET to resolve the issue.

If you log in to multiple software HIP Services as the same user, the remote session for the first HIP Service will be terminated.

Workaround: None.

Currently, users with the Network Administrator role in the Conductor can see and grant provisioning requests but are unable to view license vouchers and make top level licensing changes.

Workaround: None.

When uninstalling the HIPclient or HIPserver, the tray icon may disappear, and the application will restart. This occurs without selecting Yes or No from the dialog.

Workaround: None.

When creating a Conductor certificate using the Create Conductor Certificate dialog, you must click Save. Pressing Enter will result in an error and the operation will not complete successfully.

Workaround: None.

Currently, HIPswitch reporting graphs do not indicate temperatures below freezing.

Workaround: None.

he HIPclient may lose access to the macOS keychain following an update.

Workaround: If this occurs, use the procedure below to resolve the issue.

1. Open the finder by pressing Command-N

2. Find the TemperedNetworksHIP application, right click it and select Show Package Contents

3. Double-click Contents

4. Double-click MacOS

5. Keep this window available, you will need it below

6. Start Keychain Access (Applications > Utilities > Keychain Access)

7. Navigate to the System keychain (on the upper left)

8. Click on Keys (on the lower left)

9. Click on the header named Kind to sort the keys

10. For each private key with the name com.temperednetworks do the following:

a. Double-click the item to open it

b. Click Access Control

c. Enter your password

d. Click the +

e. Drag the tnw-hipd from the window opened earlier and drop it into the window you opened by tapping +

f. Click tnw-hipd, then click Add - the window will close

g. Click Save Changes

h. Make a note of your username, you will need this in a moment.

i. Enter your password and tap Allow

j. You will be prompted to enter your username and password. Do so and close the com.temperednetworks window.

Repeat step 10 for each private key named com.temperednetworks. You will have one key for each HIPclient profile you created.

Link Manager default settings do not work between Conductors running on Azure using the Azure Network Security Group setting and wireless HIPswitches.

Workaround: You must Disable pings on active link on each Wireless HIPswitch or set an alternate active ping target (e.g. 8.8.8.8).

You must be a manager of every overlay that contains any device associated with all HIPservices in a HIP Service group, otherwise you lose the ability to make edits to that HIP Service group. There is no error message or any explanation as to why you are not allowed to make edits.

Workaround: None.

The HIPswitch Limit Bandwidthsetting currently displays as bytes per second instead of bits per second.

Workaround: None.

When connected via serial console to a HIPswitch 150, pasting text ~35+ characters into the console requires the console to be disconnected and reconnected to restore functionality.

Workaround: None.

In tag properties, if you enter a month value in the Expire tag usage field, such as 1M, it is converted to weeks and days when the change is applied.

Workaround: None

After installing a windows HIPclient using the unintended install method, the tray application does not start.

Workaround: Start the application manually after installation is complete

Diagnostic mode displays a drop-down menu for selecting a preferred radio access technology, however the backend does not correctly handle this setting.

Workaround: None.

Client authentication does not display an error message when authentication fails due to the absence of a Conductor connection.

Workaround: None

When enabling SNAT on a HIPswitch, new connections will begin to use the overlay gateway IP address of the HIPswitch, but existing connections will not use the SNAT address until the connection is idle for the specified connection TTL or if the HIPswitch is rebooted.

Workaround: Reboot the HIPswitch after enabling SNAT.

The time on a standby Conductor and master conductor can become out of sync and cause missing traffic stats and health data from HIPswitches.

Workaround: When failing-over an HA-paired Conductor, verify that the timestamps are the same.

In rare cases, an HIPswitch running in Azure may fail to reconnect to the Conductor after a firmware upgrade.

Workaround: Restart the HIPswitch VM. Please note it can take up to 10-15 minutes to come back online.

If a device stops communicating, the Conductor UI may not reset the activity display to gray, reporting online status incorrectly.

Workaround: Reload the browser.

In rare cases, a Conductor HA pair may stop syncing.

Workaround: If this occurs, promote the HA-secondary to primary, then re-pair them.

Pinging an Azure-hosted HIPswitch from another HIPswitch will fail in the Conductor UI. This is due to ICMP being denied by Azure's security groups.

Workaround: None

Toggling policy too quickly on a HIPswitch running on Google Cloud can result in the route table becoming out of sync when using route injection.

Workaround: After toggling policy, wait 10 seconds before toggling it again.

HIPclients and HIPservers are currently not compatible with 1.1.1.1 DNS service.

Workaround: None

The bandwidth check in the HIPswitch Diagnostics tab may fail for HA-paired HIPswitches.

Workaround: None.

If you place a Conductor in diagnostic mode and have a non-standard port configuration defined, it may not respond to ping commands. The diagnostic mode functionality should be otherwise unaffected.

Workaround: None.

When configuring Wi-Fi settings in diagnostic mode, the HIPswitch may override the configuration on reboot if Wi-Fi configuration was configured in the Conductor previously.

Workaround: Factory reset the HIPswitch before entering diagnostic mode.