Lantronix CoBox Device Servers Software Release Notes Version V4.4 July 2, 2001 Copyright 2001, Lantronix Release notes are also available on the Lantronix web site (www.lantronix.com) and via anonymous FTP from ftp.lantronix.com. Contact Lantronix or your reseller for more information. This document describes the Lantronix CoBox Device Server firmware release. =============== RELEASE SUMMARY =============== Current release: V4.4 ============================= ADDITIONAL PRODUCTS SUPPORTED ============================= V4.4 supports the CoBox Mini, CoBox Mini100, and CoBox-FL, as well as the CoBox Micro, UDS-10B, and DR1 products. ================= FIRMWARE RELEASES ================= CBXnnn.rom: Supports old HW platforms, without encryption. LTXnnn.rom: Supports all of the new HW platforms, without Token Ring functionality, without encryption. LTXEnnn.rom: Supports all of the new HW platforms, without Token Ring functionality, with encryption. ============ NEW FEATURES ============ The following topics describe the new features of the firmware: 1. Security 2. Telnet Mode 3. Modem Mode 1. Security The strategy on security parameter "disable websetup" has been changed. Previously, when you disabled the web setup, both the web server and TCP port 77FEh (configuration port) were disabled. You now have the option of disabling the configuration port TCP 77FEh, but at the same time using the web server for something else. To disable port 77FEh, set the parameter "disable port 77FEh." 2. Telnet Mode The interpretation of LF has been removed. LF is sent as LF instead of CR/LF. 3. Modem Mode The LF/CR combinations were changed to CR/LF. The use of these characters was inconsistent and caused trouble in some applications. Such applications always expected these characters as CR/LF, but in some states the firmware sent LF/CR. Now it always sends CR/LF. ============== FIXED PROBLEMS ============== The following topics describe problems fixed by this release: 1. DHCP 2. Handling of RS485 2-wire for the AMD HW platform 3. Active connect timeout for connect mode 0xn2 4. Check for DHCP while using an AutoIP IP address 5. Setting IP addresses 1. DHCP Once a Device Server obtained an IP via AutoIP, it would send out DHCP requests on the subnet of the AutoIP address obtained. This is wrong. The request must be sent out as a general broadcast. This release fixes the problem. 2. Handling of RS485 2-wire for the AMD HW platform The calculation for the switching time between Transmit and Receive was not accurate for the AMD, so some break time between the next-to-last character and the last character could occur. This break time could lead to some trouble in special applications that need precise timing. 3. Active connect timeout for connect mode 0xn2 We reset the active connect timeout for connect mode 0xn2. Previously, once the DTR was removed, the timeout was not reset to its default value. It continued to retry the connection every four seconds instead of starting with a smaller timeout as it is supposed to. 4. Check for DHCP while using an AutoIP IP address Previously, once a Device Server obtained an IP via AutoIP, the Device Server would no longer accept a DHCP IP address. The Device Server now checks for DHCP addresses while using an AutoIP IP address. 5. Setting IP addresses Before this release, we had the following strategy for entering IP addresses in the setup: You can simply acknowledge existing settings by pressing the Enter key. If the first value of the IP address is set or acknowledged as '0', all remaining parts of the IP address were set to '0' automatically. With the previous releases we added functionality requiring you to enter an IP address such as 0.0.1.55. Once you set this value and went through the settings again, the firmware acknowledged the first part with '0' and everything was cleared to '0', which deleted the settings '1' and '55'. This behavior is no longer desired. From now on the firmware does not reset values to '0' if the first part is acknowledged with '0'. ========== Known Bugs ========== 1. This release cannot be used in combination with Cobox-E2. 2. Sendcharacters on Channel 2 do not work correctly as Channel 2 uses the setting of Channel 1 for this particular feature. 3. DHCP might still cause trouble, especially with non-responding DHCP servers and small leasetimes. This problem will be solved from Release 4.5B4 onwards.