Release Notes 2.1.6

Release Date: March 1, 2019

What's New

New in this release:

Modbus TCP to RTU Gateway
We’ve enhanced our Serial over IP (SoIP) feature with a Modbus TCP to Modbus RTU gateway. After configuring Modbus via the HIPswitch SoIP settings in Conductor, the HIPswitch will accept Modbus TCP commands from servers, issue the commands to serially-connected Modbus RTU device(s), and return the responses via Modbus TCP back to the server. The HIPswitch accepts pipelined requests from the server(s). This provides optimal efficiency for Modbus traffic in terms of throughput, latency, and number of messages as compared to transparent Serial over IP.
DHCP Relay
HIPswitches can now relay DHCP requests to a central DHCP server as an alternative to your existing DHCP server. This allows additional deployment flexibility where extended DHCP options are needed, or an existing DHCP server integrates with other systems such as Active Directory and DNS.
Note: When moving devices from one HIPswitch to a different one, the central DHCP server may issue the same IP address to the device, which could result in policy or routing conflicts depending on your network.
Wireless Underlay Failsafe

The HIPswitch Link Manager, introduced in version 2.1.0, intelligently monitors the health of the underlay connection, detecting when there are no options for the HIPswitch to connect to Conductor or peer HIPswitches. Link Manager is now enhanced to reboot the HIPswitch which may restore the wireless connection to a healthy state. Occasionally, changes made in the wireless provider network will drop or hang a cellular or Wi-Fi HIPswitch uplink in such a way that the modem cannot recover. Rebooting the HS will force the modem and cell tower or access point to renegotiate their connection; sometimes this restores a healthy connection. This behavior is on by default for wireless models, and can be disabled and configured per HIPswitch in the Conductor UI. You can configure the amount of time Link Manager waits to reboot the HIPswitch after first detecting underlay failure, and a minimum amount of time to wait between reboot attempts. By default, all wireless models enable this feature with a wait-to-reboot value of 10 minutes, and min-wait-between-reboots value of 30 minutes.

Note: See known issue DEV-9877 for additional information in reference to running a HIPswitch on the Microsoft Azure platform.
APAC Modem Support
The HIPswitch cellular expansion module SFF-MOD-MC7430 (PLF-0118-01) is now available for the HIPswitch 150, which includes the Sierra Wireless MC7430 modem for operation in Hong Kong, Macau, and Japan.
Note: Firmware release 2.1.6 is required to use this expansion module.
HIPswitch 250 Series Revision 2 Support
The HIPswitch 250 Revision 2 is now available and includes the following SKUs:
  • HIPswitch 250e (PLF-0062-02)
  • HIPswitch 250g (PLF-0066-02)
  • HIPswitch 250gd (PLF-0111-02)

Revision 2 provides improved SFP compatibility, modem watchdog support, and improved modem carrier compatibility.

Note: Firmware release 2.1.6 or higher is required to use Revision 2 of the HIPswitch 250.
Wired Interface Support for Android
The HIPclient for Android now supports wired ethernet connectivity.
Tag integration with HIP invitations
You can now specify tag(s) for HIP invitations, which apply to HIP services as they activate. This makes it easy to organize newly-activated HIP services and, when combined with smart device groups, automatically give them communications policy in overlay networks.
Longer HIPswitch UIDs
HIPswitches which are licensed with a 2.1.6 or higher firmware may generate a longer serial number portion of the UID (up to 20 characters), compared to the previous 12 characters. HIPswitches licensed from a previous release will not change their UID.

Upgrade Considerations

The 2.1.6 release includes all hotfixes from prior releases and addresses all known support cases at the time of release.

We recommend you upgrade to 2.1.6 if:
You want to take advantage of performance and stability increases in 2.1.6, or use any of the following features: You were impacted by any issues discovered in prior releases, especially if you have any of the following:
  • Modbus RTU to Modbus TCP proxy
  • HIPswitch DHCP relay
  • HIP invitation Tag integration
  • New hardware support
  • HIPswitch 250 cellular instability
  • HIPswitch 150 cellular instability
  • Remote Linux HIPserver HIP tunnel instability
  • HIPswitch 75 memory instability
Note: You may upgrade Conductor directly to 2.1.6 from version 1.12.6 or later. You may upgrade HIPswitches to 2.1.6 provided you are running Conductor 2.1.6.

Extensive testing was conducted both in-house and with selected development partners, in lab and in production environments to ensure that performance is equivalent to 2.1.5. Additionally, 2.1.6 should be more stable than all prior releases.


ID Applies to Description
DEV-9795 HIPclient, Windows Fixed an issue in the Windows HIPclient where a MAP connection was required for the HIPclient t begin passing traffic.
DEV-9787 HIPswitch Fixed an issue where incorrect health data was reported while a HIPswitch was in transparent mode
DEV-9771 HIPclient, Windows Fixed an issue where the Windows HIPclient networks view would not report all available data.
DEV-9709 HIPclient, iOS Fixed an issue where HIPclient profiles created from HIP invites on iOS devices using the same Apple ID were synced due to iOS clipboard behavior.
DEV-9639 OpenHIP Fixed an issue where a HIPswitch sends update acknowledgements to the wrong address.
DEV-9601 HIPclient, Android Fixed an issue where the 2.1.5 Android HIPclient was reported incorrectly in the Conductor as version 2.1.4
DEV-9595 HIPclient, Android After an Android device running a HIPclient wakes, ping now correctly resumes.
DEV-9593 HIPclient, Android It is no longer possible to delete the current active profile, which would cause unpredictable behavior with the HIPclient.
DEV-9574 Conductor Fixed an issue where updating system settings after a proxy password has been entered may overwrite it with random data.
DEV-9560 HIPswitch Fixed an issue that could cause packets on an overlay network to transmit on the underlay network under certain conditions.
DEV-9472 HIPclient, Windows Fixed an issue with the Windows HIPclient where deleting a profile using the CLI would not update the HIPclient UI correctly, resulting in discrepancies in the profile list.
DEV-9477 Conductor Fixed an issue in the Health Data tab where selecting more... would not display additional lines.
DEV-9389 API POST /api/v1/people/{id}/tags in the Conductor API now presents clearer, more actionable error messages.
DEV-9382 Conductor Improved dialog information when attempting to update firmware with an image not compatible with the target platform. The dialog text now clearly states the firmware is incorrect, replacing the generic non-actionable error message.
DEV-9385 HIPclient, Android Fixed an issue where profile selection is disabled after creating a new profile and restarting the Android HIPclient.
DEV-9382 Conductor Fixed an issue where attempting to install a non-Azure firmware package in an Azure instance would produce an error message stating <inserv form image>.
DEV-9377 Diagnostic mode Fixed an issue that would allow you to enter an invalid gateway address in diagnostic mode.
DEV-9366 Cellular Raised the log level of cellular interface repair messages to provide information about when a cellular interface is being repaired.
DEV-9333 Conductor The Standby Conductor in an HA pair will now correctly display the Diagnostics Tab in the UI.
DEV-9317 HIPswitch Fixed an issue where a firmware upgrade may fail due to a timing issue, taking the HIPswitch offline until it is restarted.
DEV-9312 HIPclient, Windows Fixed an issue where an overlay IP address displayed on the Configuration settings, but not in the HIP Networks view.
DEV-9269 HIPclient, Windows Fixed an issue where the Windows HIPclient would display an incorrect underlay IP address.
DEV-9259 Conductor HIPclient descriptions now correctly display in the Devices Reference file from the PCI downloads page.
DEV-9201 HIPswitch 75w Fixed an issue where the HIPswitch 75w would not properly connect to Wi-Fi after a factory reset.
DEV-9106 HIPclient, iOS Fixed an issue where you were required to stop and start the HIPclient to resume traffic when failing over from cellular to Wi-Fi.
DEV-9091 HIPclient, Android Trailing spaces are now stripped when manually entering the Conductor URL on the configuration settings.
DEV-9013 HIPswitch 75w The WiFi LED now correctly functions on the HIPswitch 75w.
DEV-7499 HIPswitch The bandwidth check in the HIPswitch Diagnostics tab no longer fails for HA-paired HIPswitches.
DEV-6446 HIPclient, iOS Fixed an issue where viewing traffic stats in the iOS app would display negative values instead of zero.

Known Issues

ID Applies to Description
DEV-9877 Conductor, Cellular HIPswitch

Link Manager default settings do not work with Conductors running on the Microsoft Azure platform when using Azure Network Security Group settings.

Workaround: If you are using an Azure Conductor with Wireless (Cellular or Wi-Fi) HIPswitches, disable pings on active link on each wireless HIPswitch or set an alternate active ping target (e.g.

DEV-9830 HIPswitch 100

The HIPswitch 100g may sometimes fail to initiate a reboot when requested from the web interface in diagnostic mode.

Workaround: Power cycle the HIPswitch.

DEV-9782 HIPclient, all platforms

HIPclient chooses an incorrect interface and cannot establish a connection with devices behind a HIPswitch running on the Google Cloud Platform (GCP).

Workaround: In the HIPclient configuration, select your desired network interface instead of allowing the HIPclient to automatically choose an interface.

DEV-9697 Conductor

Removing Conductor HA does not remove the standby Conductor's address from the HIPswitch Conductor search list on HIPswitches running versions previous to 2.0.

Workaround: None

DEV-9397 Conductor

Factory resetting a Conductor that's in an HA-pair doesn't work correctly the first time.

Workaround: Factory reset the Conductor a second time to resolve the issue.

DEV-9166 HIPswitch, Cloud

When route injection is enabled, a HIPswitch protected subnet must contain only one HIPswitch. Additionally, any custom routes added to the route table are deleted when route injection is enabled.

Workaround: If you want to deploy multiple HIPswitches in the same protected subnet or keep your custom routes, disable route injection.

DEV-9157 HIPclient, macOS Killing the hipctl daemon (tnw-cltd) will result in the HIPclient not functioning properly.

If you try and run any hipctl commands, the message Could not connect with Tempered Networks control process is displayed. No message is displayed when trying to make changes from the configuration UI.

Workaround: Restart the process by entering sudo launchctl start com.temperednetworks.ctld from a terminal.

DEV-8097 HIPclient, macOS If your computer has multiple active NICs and you select a specific NIC in your HIPclient configuration, the operating system will choose the NIC for outbound traffic.Workaround: None
DEV-8060 Conductor

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

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

DEV-8051 Conductor The IP address field on associated with a HIPswitch may be blank on the HIPservices tab.Workaround: You can locate the IP address information under the Reporting tab.
DEV-7955 Conductor

If you ping a HIPswitch running in Azure from another HIPswitch, it will fail in the Conductor UI. This is due to ICMP being denied by Azure's security groups.

Workaround: None

DEV-7769 Conductor

Toggling policy on and off too quickly on a HIPswitch hosted in 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.

DEV-7661 Conductor

When replacing a HIPswitch, the new HIPswitch may take a few minutes to reconnect and appear online in the Conductor.

Workaround: Wait a few minutes after replacing the HIPswitch for it to display in the Conductor UI.

DEV-7125 Conductor, PCI

When exporting PCI data, HIPservices references may not display correctly when viewing the CSV file in Microsoft Excel.

Workaround: None

DEV-7058 HIPswitch

When reconfiguring your underlay network from one physical port to another in the Conductor, the changes may not be applied successfully and the configuration will revert back to the original settings.

Workaround: Make the configuration changes in diagnostic mode.

DEV-6590 Conductor You can add a voucher code more then once from the Licensing tab. This does not create additional licenses, but is visually confusing.Workaround: None
DEV-6587 Conductor The Licensing tab may display invalid entries.Workaround: Remove the invalid items manually.
DEV-6533 Conductor

When creating or editing a smart device group, rules can have the same ordinal values. This can cause unintended issues in the processing results.

Workaround: When creating rules, verify each rule has a unique ordinal value.

DEV-6226 Conductor

A fully qualified domain name cannot be used for local or peer replication addresses on an HA Conductor pair.

Workaround: None

DEV-6195 Conductor

The Conductor incorrectly displays an option to check bandwidth for HIPclients in diagnostic view. This option is not supported for HIPclients and will not function correctly if selected.

Workaround: None

DEV-5832 HIPswitch

Device NAT functionality currently does not work with layer 2 traffic.

Workaround: None

DEV-5530 Conductor UI In some cases, Allow incoming pings (ICMP) and SYN Flood Protection on the Firewall page may be disabled and won't toggle.

Workaround: Refresh your browser to resolve the issue.

DEV-5430 Conductor After configuring a Conductor for the first time, you may receive a Lost connection to the original server message if you select Return to settings too quickly.

Workaround. Wait at least 20 seconds before selecting Return to settings.

DEV-5008 PCI Reporting PCI Reporting shows the UUID reference instead of the name when generating a PCI report from Settings > Advanced > PCI Reporting > Downloads > User Activities Report.

Workaround: To view names, you can download object references from the same page where you generated the PCI report.