UT-Family Firmware History (Including UT-Soft)

This is the firmware revision log for the UT family bridges.

----------

This release corrects the following:

The NDIS 6.x DCB Virtual Ethernet Adapter driver would throw an error when it received a maximum sized 802.1Q Ethernet packet. The driver did not account for the additional overhead of the VLAN tag.

UTSoft was modified to detect and discard empty Ethernet packets.

----------

This release patches a security vulnerability in the web server “CGI-session” authentication method.

The firmware was modified to ignore ICMP timestamp requests on the untrusted interface.

----------

This release patches a security vulnerability in the web server “CGI-session” authentication method.

The firmware was modified to ignore ICMP timestamp requests on the untrusted interface.

----------

UTSoft for Windows 11. This version contains the newly developed NDIS 6.x DCB Virtual Ethernet Adapter driver that meets the install and signing requirements for Windows 11. Please note that this version is compatible with Windows 10 64-bit systems and is recommended for new installs.

A feature was added that allows the [X] “Close Window” button in the top right corner of the UTSoft Window to be disabled. This is intended to make it more difficult for a user to inadvertently close the UTSoft application when they really intended to minimize the window. The close window button is disabled by adding the command-line argument “-noclose” to the UTSoft shortcut.

UT-Soft Windows 10/11 README
--------------------
There are two UTSoft installers included in this distribution. One is targed for Windows 11 systems, the other is for older Windows systems. Both installers contain the exact same copy of the UTSoft client. The difference is with the DCB Virtual Ethernet Adapter driver. The Windows 11 installer has a newly developed NDIS 6.x driver that meets the signing requirements for Windows 10 64-bit and Windows 11 systems.

Since most new systems are 64-bit and are running Windows 10 or Windows 11, we recommend using the Windows 11 installer for either system. In the event that you later upgrade the Windows 10 system to Windows 11, the proper driver will already be installed.

For 32-bit systems or Windows XP through Windows 8.1, please use the non-windows 11 installer. This installer contains our older NDIS 5.x driver that meets the signing requirements for Windows 7, 8, and 8.1.

Please contact DCB support if you have any questions.

----------

Web server support for TLS v1.1 has been removed. The web server will now only support TLS v1.2.

A new web server certificate can be generated without the use of a USB flash drive. This will allow users to replace an expired certificate without having physical access to the unit. (Administration - New Web Certificate).

This release corrects the following:

Fix protocol in the terminal server. The telnet protocol inserts a null byte after a single carriage-return character. The null byte should be removed from the data stream before output to a serial port.

Fix blocked-write in the terminal server. An output overflow condition could potentially lockup the terminal server.

----------

Fix protocol in the terminal server. The telnet protocol inserts a null byte after a single carriage-return character. The null byte should be removed from the data stream before output to the serial port.

Fix blocked-write in the terminal server. An output overflow condition could potentially lockup the terminal server.

----------

This includes addressing the SWEET32 vulnerability in TLS and disabling support for TLS v1.0. The web server will only support TLS v1.1 and v1.2. As a result, users relying on Windows XP to configure the UT may find that they can no longer connect to the web server.

----------

This includes addressing the SWEET32 vulnerability in TLS and disabling support for TLS v1.0. The web server will only support TLS v1.1 and v1.2. As a result, users relying on Windows XP to configure the UT-3302 may find that they can no longer connect to the web server.

----------

UT-Soft can now be configured to dynamically insert a host route to the UT-Server via the currently active gateway. This route is added prior to enabling link on the DCB Virtual Adapter. The purpose is to protect the route to the UT-Server in the event that the DCB Virtual Adapter has a default gateway configured or is obtaining an IP address automatically.

UT-Soft can be configured to route WAN traffic either through the local gateway or though the remote gateway.

Please review the document UTSoft_2_4_Overview.pdf for a detailed description of these features. This document is now included with the user manual.

----------

Support for managing multiple configuration files within UT-Soft. A new dialog was added that allows the user to select, edit, or create configuration files.

Support for storing the configuration files in an encrypted format. Encryption is AES-256. The key is generated from a user-supplied password.

Support for storing the Virtual Adapter's IPv4 configuration in the configuration file and applying the IPv4 configuration when UT-Soft connects.

Support for storing IPv4 routing table entries in the configuration file and applying the routes when UT-Soft connects.

Support for IPv4 packet filtering as packets are sent/received with the server.

Support for TCP mode. This allows UT-Soft to inter-operate with an ET server or an XT server in TCP mode.

Note: This version is backward compatible and may be installed on top of an existing installation without losing the configuration.

----------

The Limit UDP Packet Size feature was extended to allow selection of the maximum UDP payload size. In the previous firmware, the maximum UDP payload size was fixed to 1412 bytes. The user may now select between 1412, 1316, 1188, and 1092 bytes. Only the 1412 size is backward compatible with older firmware. If a smaller size is selected and one of the units is running older firmware, the connection will fail with a time-out.

NOTE: The purpose for adding the smaller UDP Payload sizes is to address the MTU issue that customers are encountering when deploying UT/XT tunnels on LTE networks.

----------

The Limit UDP Packet Size feature was extended to allow selection of the maximum UDP payload size. In the previous firmware, the maximum UDP payload size was fixed to 1412 bytes. The user may now select between 1412, 1316, 1188, and 1092 bytes. Only the 1412 size is backward compatible with older firmware. If a smaller size is selected and one of the units is running older firmware, the connection will fail with a time-out.

NOTE: The purpose for adding the smaller UDP Payload sizes is to address the MTU issue that customers are encountering when deploying UT/XT tunnels on LTE networks.

----------

The Limit UDP Packet Size feature was extended to allow selection of the maximum UDP payload size. In the previous firmware, the maximum UDP payload size was fixed to 1412 bytes. The user may now select between 1412, 1316, 1188, and 1092 bytes. Only the 1412 size is backward compatible with older firmware. If a smaller size is selected and one of the units is running older firmware, the connection will fail with a time-out.

NOTE: The purpose for adding the smaller UDP Payload sizes is to address the MTU issue that customers are encountering when deploying UT/XT tunnels on LTE networks.

----------

The Limit UDP Packet Size feature was extended to allow selection of the maximum UDP payload size. In the previous firmware, the maximum UDP payload size was fixed to 1412 bytes. The user may now select between 1412, 1316, 1188, and 1092 bytes. Only the 1412 size is backward compatible with older firmware. If a smaller size is selected and one of the units is running older firmware, the connection will fail with a time-out.

NOTE: The purpose for adding the smaller UDP Payload sizes is to address the MTU issue that customers are encountering when deploying UT/XT tunnels on LTE networks.

----------

----------

----------

This release corrects the following:

There was a race condition in the tunnel fail-over feature that could result in a client simultaneously connecting to both the primary and alternate server. Any unit configured with fail-over backup connetions should install this update.

If DHCP is enabled and a DHCP lease is lost, the device would receive a new address, but the DNS requests would continue to be sent using the defunct IP address. This would result in never receiving a DNS reply and failure to resolve a name. This type of failure is likely to occur only when a router, also acting as a DHCP server, goes down for a period of time longer than the DHCP lease.

----------

This release corrects the following:

There was a race condition in the tunnel fail-over feature that could result in a client simultaneously connecting to both the primary and alternate server. Any unit configured with fail-over backup connetions should install this update.

If DHCP is enabled and a DHCP lease is lost, the device would receive a new address, but the DNS requests would continue to be sent using the defunct IP address. This would result in never receiving a DNS reply and failure to resolve a name. This type of failure is likely to occur only when a router, also acting as a DHCP server, goes down for a period of time longer than the DHCP lease.

This release contains the following modification:

When the unit is reset to defaults, it will generate a new random web certificate instead of using a static default certificate. Even though the end-user can manually generate a certificate, this will insure that each device starts out with a unique certificate.

----------

This release corrects the following:

There was a race condition in the tunnel fail-over feature that could result in a client simultaneously connecting to both the primary and alternate server. Any unit configured with fail-over backup connetions should install this update.

If DHCP is enabled and a DHCP lease is lost, the device would receive a new address, but the DNS requests would continue to be sent using the defunct IP address. This would result in never receiving a DNS reply and failure to resolve a name. This type of failure is likely to occur only when a router, also acting as a DHCP server, goes down for a period of time longer than the DHCP lease.

NOTE: This release coincides with correcting the flash memory corruption abnormality during the firmware update process for some units in the field. Although no firmware modification was required to correct this problem, this release can be used as a marker to determine if the customer should take precaution when installing firmware.

If currently running firmware prior to v1.21, and the unit is in the serial number range 59103115 - 59103205 or 58800083 - 58800087, prior to updating firmware, the "pre" firmware must installed first, then immediately install the standard firmware, without power cycling the unit. The "pre" version is fully functional firmware, so this two-step upgrade process can be performed remotely. If a unit is in this serial number range and this procedure is not followed, the unit may become non-functional during the update.

----------

UT-Soft V2.1 Release Notes 11/15/2016

This release adds the following feature:

A VLAN tag option was added to the configuration. This will allow UTSoft to inter-operate with a UT Server connected to a VLAN tagged trusted network.

When the VLAN tag option is blank, UTSoft will work as usual with untagged packets. When a VLAN tag is entered, UTSoft will only accept Ethernet packets carrying a matching tag. In addition, UTSoft will add the VLAN tag to packets sent upstream to the UT Server.

Note: This feature was originally added to UTSoft v1.8 as an experimental feature. UTSoft v1.8 was never formally released and the feature subsequently disabled in UTSoft v1.9.

----------

1.0 INTRODUCTION

This release corrects the following:

- error handling daylight saving time when setting the clock

This release adds the following feature:

- support for externally signed SSL web certificates

This release addresses the following newly discovered security issues:

- check web URL parameters for cross-site scripting and hazardous input

- modify the web server to issue "Cache-control no-store" in the header

- modify the web server to issue "404 - Not found" error instead of "403 - forbidden" when browser attempts access to a restricted page

- configure the web server to refuse low and medium strength ciphers

- configure the web server to refuse TLS compression (CRIME vulnerability)

- update openSSL from v0.9.8k to v1.0.2g to address multiple vulnerabilities (eliminate ssl2/ssl3, eliminate insecure renegotiation, POODLE, DROWN)

Note: Previous version, v1.19, was a test release sent to select customers.

----------

----------

1.0 INTRODUCTION

Note: This includes the previous version, v1.17, which was a test release.

This release corrects the following:

- Remote syslog did not work across a VLAN.

This release adds the following features:

- Modbus monitoring tool, same feature as implemented on the UT-6602.

- Disabled negotiation of SSLv3 protocol in the web server.

----------

----------

1.0 INTRODUCTION

This release adds support for a new NAND flash device used in current hardware. Once a unit has been upgraded to v1.15, it cannot be reverted back to older firmware. This is to protect against installing old firmware on a new device.

----------

This release corrects the following:

- The NTP client would not work on LAN1 when VLAN mode was enabled.

----------

1.0 INTRODUCTION

This release note includes v1.12, which was not officially released.

V1.12 corrected a bug with the "Accepted Web Access Source Addresses". Once set, the rules could not be cleared.

V1.13 adds most of the features requested by utility companies for Critical Infrastructure Protection Systems (CIPS) compliance. These include:

- Session type authentication with logout feature. This feature is optionally enabled, otherwise the device will continue to use HTTP basic authentication.

- User defined login banner.

- Optional password enforcements: Minimum length, upper/lower case, special characters, numeric characters, age.

- Status feature to display all open and listening TCP and UDP ports.

- Feature to individual enable/disable each Ethernet port on the LAN1 switch

- Feature to disable the serial setup port.

- 802.1Q vlan tag/untag for the LAN-1 ports. This feature requires the UT-3302 to have an IP175D switch controller.

----------

----------

----------

----------

Adds most features requested by CIPS customers. These include:
- Session type authentication with logout feature. This feature is optionally enabled, otherwise the device will continue to use HTTP basic authentication.
- User defined login banner.
- Optional password enforcements: Minimum length, upper/lower case, special characters, numeric characters, age.
- Status feature to display all open and listening TCP and UDP ports.
- Feature to individual enable/disable each Ethernet port on the LAN1 switch
- Feature to disable the serial setup port.
- 802.1Q vlan tag/untag for the LAN-1 ports. This feature requires the UT-3302 to have an IP175D switch controller.
- Correct a problem with the "Accepted Web Access Source Addresses". Once set, the rules could not be cleared. This release includes internal versions 1.12 and 1.13 which were not released.

----------

UT-6602. V1.08 Release Notes 01/24/2011

1.0 INTRODUCTION

Change for new hardware compatibility.

----------

UT-3302. V1.09 Release Notes 9/22/2010

1.0 INTRODUCTION

This release adds the capability of setting a secondary (or alias) address for each interface. This was a feature from the UT-3300 that wasn't carried over to the UT-3302.

This release fixes a minor problem in serial setup. If the user selects DHCP mode for LAN1, the only way to return the unit back to a static address from serial setup was to reset all options to defaults.

----------

UT-6602. V1.07 Release Notes 9/22/2010

1.0 INTRODUCTION

This release adds the following feature:

- A new tool was added to the tools page. This tool, when enabled, allows the UT-6602 to be monitored via the ModBus/TCP protocol. The UT-6602 will report the status of 4 items using the following modbus registers:

10001 Tunnel Mode 0=Server, 1=Client

10002 Target-1 0=Not Responding, 1=Responding

10003 Target-2 0=Not Responding, 1=Responding

10004 Tunnel Client 0=On Backup, 1=On Primary.

The above information is also reported on ModBus registers 20001 - 20004, 30001 - 30004, and 40001 - 40004. Registers 10002 and 10003 refer to network devices, specified by IP address. If the UT-6602 can successfully ping the network device, then it is flagged as responding.

Note: If the UT device is configured for both Server and Client mode, register 10001 will report 1. If the UT device is configured for Server mode, register 10004 will always report as 1.

----------

UT-3302. V1.08 Release Notes 4/6/2010

1.0 INTRODUCTION

This release adds the following features: - A new option was added to LAN2, called "monitor link". When set to "yes", LAN2 will be monitored for link loss. Whenever link loss is detected, the DHCP client will immediately go to the renew state. This will allow the unit to quickly switch to a new network if the cable is unplugged from one network and moved to another.

- The serial port (setup port) can now be configured for UDP-Serial (Etherpoll compatible) mode or for a TCP-Server mode. When either of these modes are selected, the setup function of the serial port is disabled.

- The unit can be set to temporarily set to defaults by pressing and holding the setup switch during power-up. The sequence is:

1) apply power, blue (bottom) led will go on then the green (top) led will go on. 2) wait for the green led to go off 3) press and hold the setup switch 4) wait for the green led to blink on then off 5) the switch may be released. 6) the serial port will be in setup mode and the unit can be accesses from the default address

Note) The default settings are not written to NV memory. The user must store the settings from either the serial port or the web interface.

----------

UT-6602. V1.06 Release Notes 6/23/2010

1.0 INTRODUCTION

The UT-6602 was unable to decode a saved configuration file written by the UT-3302. This is a problem for customers that are replacing a UT-3302 server with a UT-6602 server and want to carry the configuration file forward. The UT-6602 was modified to detect and decode a UT-3302 configuration file.

----------

UT-6600/6690. V1.06 Release Notes 11/20/2009

1.0 INTRODUCTION

Th This release corrects the following:

- The default gateway field was missing from the PPP configuration.

- Help screens were missing for PPP configuration.

----------

UT-3302. V1.07 Release Notes 11/11/2009

1.0 INTRODUCTION

This release adds support for the new Integrated Switch IC version. This update is not required on older equipment and will not change their operation.

----------

UT-3302. V1.06 Release Notes 10/27/2009

1.0 INTRODUCTION

The integrated switch did not allow packet switching between the ports, but only between the CPU and the port. The switch is now configured to allow packet switching between the ports.

----------

UT-6690 V1.05 Release Notes 10/15/2009

This is the initial release of UT firmware for the UT-6690.

----------

UT-Soft. V1.6 Release Notes 10/08/2009

This release adds support for Vista, Vista x64, Windows 7, and Windows 7 x64. The installer detects the system type and automatically installs the appropriate driver.

----------

UT-3302. V1.5 Release Notes 9/25/2009

1.0 INTRODUCTION

This is the initial release of the UT-3302 firmware. The version is starting with v1.05 to show its relationship to the other UT products.

----------

All UT-hardware. V1.5 Release Notes 8/10/2009

1.0 INTRODUCTION

This release changes the behaviour of the virtual adapter Ethernet link state. Previously the virtual adapter would report "link-up" while UT-Soft was running and "link-down" if it was not running. Now, the virtual adapter will report "link-up" when UT-Soft is running and connected to the server. If UT-Soft is not running or if is not connected the virtual adapter will report "link-down". This change was requested by a customer. The Telex C-Soft software needs the link-down change in order to cause an alert on the console when the connection is lost. (Note, this modification was made in V1.4, but V1.4 was not distrubited.)

----------

All UT-hardware. V1.05 Release Notes 7/22/2009

1.0 INTRODUCTION

This release corrects the following and adds IGMPv2 support:

- IGMP snooping code did not properly handle IGMPv2 reports.

- IGMP proxy code did not compute the correct checksum for IGMPv2 query messages.

- Group specific IGMP query messages were incorrectly flooded to all hosts. They should be subject to the snooping table.

- There was a race condition between starting the IGMP report proxy and bringing up the trusted Ethernet interface. If the report proxy started first, it would fail because a multicast interface had not been designated.

This release adds the following features:

- Added an option to select either IGMPv2 or IGMPv3 as the default for proxy query. Will default to v2 since this is the version the Telex IP-223 support. Using IGMPv2 in Telex applications eliminates the need for the IGMP report proxy since the IP-223 correctly responds to all IGMPv2 queries.

- Added an option to set the number of missed IGMP reports before a multicast channel is purged. Previously this was hard coded to 3.

- Additional status information added to IGMP sooping table. The table will display an UpTime field showing how long a host has been listening to a particular multicast channel. It will also show the count of missed reports since the last received report.

----------

UT-3300, UT-6601, UT-6602 Version 1.3 6/15/2009

1.0 INTRODUCTION

- Limit UDP option. When enabled, UT-soft will limit the size of the UDP packets sent on the untrusted side to 1412 bytes. This will prevent IP fragmentation on networks with an MTU of 1500 bytes. In order to use this option, the UT-6602, UT-6601, or UT-3300 server must be running firmware version v1.3 or later.

----------

UT-Soft Version 1.03 4/7/2009

1.0 INTRODUCTION

UT-3300, UT-6601, UT-6602 Version 1.04 6/15/2009

1.0 INTRODUCTION

- Fixed bogus memory allocation error message written to the tunnel log whenever a IP, UDP, or TCP filter was enabled.

This release adds the following feature:

- Limit UDP option. When enabled, the unit will limit the size of the UDP packets sent on the untrusted side to 1412 bytes. This will prevent IP fragmentation on networks with an MTU of 1500 bytes. In order to use this option, all units must be running firmware version 1.4 or later. UT-Soft must be running v1.3 or later. This option is configured from the "Ethernet Tunnel - Advanced" web page.

----------

UT-6602 1.03 4/7/2009

1.0 INTRODUCTION

- Etherpoll functionality may be enabled on the serial setup port. Operation is compatible with the Etherpoll, however, the setup port does not implement any control signals, so there is no support for flow control or pin 6 control. Also, the timing is not as tight as the Etherpoll. Under light load, the TxTimer may vary up to 15ms.

- Reconfigured the kernel to run in preemptive mode in an attempt to reduce serial port latency.

- The bridging code was modified to drop oversize Ethernet frame before they cause a driver error. Also, when an oversize Ethernet frame is detected, the frame is probed for an 802.1q VLAN tag. If one is present, the Ethernet MTU will be automatically adjusted to accommodate the larger 802.1q frames.

- A variation of the UT-6602 called the UT-6602MC has been created. This is an internal development version and not released. - When the Etherpoll functionality is enabled, there is no serial setup. If the user needs to reset the unit to defaults, this can be done using the mode switch on the front of the unit. The process is to apply power to the unit. On the Alix.2 board, the BIOS will illuminate all 3 LEDs, then turn off LEDs 2 and 3. On the Alix.6 board the BIOS will illuminate LEDs 1 and 2, then turn off LED 2. At this point, the user needs to press and hold the mode switch until LED 2 is flashed (about 8 seconds later). The user may then release the switch. The unit will be running on default values and the serial setup re-enabled. The default values are not automatically stored. (note: The mode switch is covered by the front label. An ice pick and x-ray vision will be required for this procedure on units with first generation panel labels.)

----------

UT-Soft 1.02 3/17/2009

1.0 INTRODUCTION

- There was an error in handling IRP cancellation. When stopping UT-Soft there was a possibility that the IRP would be canceled in the wrong context resulting in a system crash or locking up the driver.

- Ethernet Address filters was not implemented. This could result in the network stack receiving a packet that was not intended for it. This was observed on our network when a remote PC was responding with a "ICMP destination unreachable" while someone was pinging a completely different machine.

- A memory fault trap was added to attempt to capture the cause of the blue-screen crashes that sometimes occur on multi-core CPUs.

Note: V1.1 was not released. It was a test version.

----------

UT-6601, UT-6602 VERSION 1.02 1/30/2009

1.0 INTRODUCTION

- The Dynamic DNS URL was not stored in the configuration file.

- The Dynamic DNS "{IP}" field was not being expanded to the IP address when contacting the DDNS service.

Note: the UT-6602 did not have these problems.

----------

UT-6601, UT-6602 VERSION 1.01 12/30/2008

1.0 INTRODUCTION

This is the initial release of the UT-6601 firmware. It is intended for customers wishing to convert their ET-6601 to an UT-6601. When converting a unit from ET to UT, it is recommended that the customer not do it remotely and that they default all parameters after the conversion.

This release corrects the following problem in the UT-6602 firmware:

- When a client communicates to the server via LAN2, the server should respond via LAN2. Likewise when a client communicates to the server via LAN3, the server should respond via LAN3. This was not the case. The server would always attempt to respond via LAN2 if it was up.

----------

UT-3300 UT-6602 VERSION 1.00 9/18/2008

1.0 INTRODUCTION

----------

Data Comm for Business Inc. 2949 County Road 1000 E Dewey, Il 61840	Voice: 217-897-6600 Toll Free: 800-4-DCB-NET Toll Free: 800-432-2638	Email: Contact Page Web: www.dcbnet.com Fax: 217-897-8023
All DCB web pages copyright ©1995- Data Comm for Business, All rights reserved. EtherPath®, EtherSeries®, EtherPoll®, EtherBridge® and EtherModem® are Registered Trademarks of Data Comm for Business, Inc.