Release Notes PN 93000531_F4 Digi Connect Wi-EM 82000983_F4 EOS June 27, 2005 INTRODUCTION This is a production release of firmware for the Digi Connect Wi-EM. The Digi Connect Wi-EM embedded device server module is one of the industry's most powerful and compact embedded system platforms that allows you to add web-enabled networking using a variety of connectivity options. It combines true "plug-and-play" functionality with the freedom and flexibility of complete product customization. SUPPORTED PRODUCTS Digi Connect Wi-EM ENHANCEMENTS None. BUG FIXES Fixed wireless connection problem where some devices were not associating with the access point. KNOWN ISSUES The current hardware doesn't allow user to set less than 6 dBm wireless transmit power. With encryption set to AES, serial throughput will be lower than usual It is not currently possible to configure the escape characters used by client applications (connect, telnet, and rlogin). When attempting to replace files in the file system, simply overwrite the existing version of the file rather than deleting the file first. Attempting to delete the file first defeats the internal file versioning maintained by the firmware, and can confuse your browser's cache. For the most consistent experience with the user interface, it is suggested that you clear your Internet cache. Microsoft Internet Explorer 6 Service Pack 1 (SP1) has a known problem where it displays the error message "Internet Explorer Cannot Open" when you use an HTTPS URL to access this Digi product. The following Microsoft article explains the problem: http://support.microsoft.com/default.aspx?kbid=812935 Due to certain browsers and their settings, the web interface may not appear proper after after a firmware upgrade. If this occurs, please clear your browser's cache or delete your browser's temporary files. When attempting to upload certificate files using Firefox, seeing an intermittent error: "Unable to upload file: invalid path (Code: -40)" CONNECTING TO THE WIRELESS DEVICE The device can only be configured over the wireless link with an access point. In order to establish a wireless link the access point must have authentication and encryption disabled. Furthermore to ensure that the Connect Wi-EM establishes a link with the correct access point the access point should use the SSID of "Connect". By factory default our device scans through each wireless channel and generates a list of access points. It then associates with the access point with the strongest signal strength. However it will choose to associate with an access point with SSID of "Connect" over another access point that has a different SSID regardless of which access point has the stronger signal strength. When the device successfully associates with an access point its link LED will go solid. CONFIGURING THE WIRELESS DEVICE Once link has been established the device can be discovered using the "Digi Device Discovery" tool. Using this tool you can find the device and if necessary assign it an IP address. Once the IP address has been determined or established you can configure it using a web browser or telnet. If at any point the device is configured in a state that it can no longer be connected to, a factory reset can be done as described below in the "RESETTING THE UNIT" section. IP ASSIGNMENT NOTES The Digi Connect Wi-EM supports three IP assignment methods: * Static IP address * DHCP * Auto-IP If a static address is enabled, it will be used. If a static address is not enabled, and DHCP is enabled, the unit will use an address supplied by a DHCP server regardless of the state of Auto-IP configuration. If a static address is not enabled, and Auto-IP is enabled, it will be used to generate an address ONLY if DHCP is disabled, or if DHCP is enabled and a DHCP server has not responded to the DHCP query. If both are enabled, Auto-IP has assigned an address, and then a DHCP server responds, the Auto-IP address will be discarded and the DHCP address will be used. RESETTING THE UNIT One feature of the Digi Connect Wi-EM firmware is an ability for a user to both soft reset the unit as well as reset the unit to its factory defaults. Both functions may be invoked via the "reset" button on the edge of the module, labelled SW1 on the board. * If the module is running (i.e. more than a few seconds after power on), holding the button for a second and then releasing it will soft reset the unit. * If the button is pressed for more than 10 seconds from the power on of the unit, it will prepare to reset the unit to its factory default state. Once the unit is prepared to reset, it will blink "1-5-1" on the red LED. Releasing the button will then reset the configuration. ADDITIONAL INFORMATION The new "set wireless transmit power" feature is not currently documented in the CLI and RCI manuals. In the CLI, it is added as a parameter on the set/show wlan command. In the "show wlan" command, it is displayed as: txpower : 6dbm and in the "set wlan" it has the following syntax: set wlan [txpower={16dbm | 14dbm | 12dbm | 10dbm | 8dbm | 6dbm}] In the RCI, it is part of the data group and its field is . The following values are valid for the txpower field: 16dbm, 14dbm, 12dbm, 10dbm, 8dbm, and 6dbm. The configuration save and restore tools will save every configurable parameter (including IP configuration) except for some related to password authentication. ENABLING THE WEB USER INTERFACE The embedded web user interface is ALWAYS available at the following URL: http://ip-address-of-device/home.htm It is also available as the default configuration interface at the following URL: http://ip-address-of-device If your device contains the Java configuration applet it can be executed by connecting to the embedded web user interface and clicking the "Launch" button on the "Home" page under the "User Interfaces". It can be made to be the default configuration interface by clicking the "Set as Default" button on the same page. The Java Configuration Applet may remain in the unit's file system without affecting the embedded web user interface. If you would like to use the Java Configuration Applet as an alternative, simply upload the index.htm file as a file with an alternate name (e.g. applet.htm). You would then be able to use the Java Configuration Applet by accessing the following URL: http://ip-address-of-device/applet.htm HISTORY 82000983_F3 Added user configurable option to set the wireless transmit power Added Poland and the Czech Republic to the list of supported wireless country codes. Fixed authentication issues with default web interface files. Fixed HTTP 400 Bad Request status seen when the password field was cleared on wireless client certificate uploads. The stored client and trusted certificates were not getting deleted in all cases. Prevent transmit gaps on small amounts of data. Limit 802.11 transmit rate to 1 and 2 mbps on Channel 14 because the hardware is not certified for higher rates. Limit the wireless transmit power to 12 when Japan is the configured country code. Certificate files are now uploaded to a hidden directory - this means any certificates that were used with the F1 binary will need to be uploaded again. 82000983_F2 Added support for multiple users and permissions Added support for TCP Keepalive Added support for remote management using the Connectware server Added support for DHCP Option 12 Added support for ADDP V2 Added support for OEM Customization WPA enhancements: - TLS, TTLS, and PEAP authentication methods - CHAP, GTC, MD5, MSCHAP, MSCHAPv2, OTP, and PAP authentication methods for use with TTLS and PEAP - Client certificates for use with TLS - Verification of server certificates - CCMP (AES) encryption Wireless networking enhancements: - Separate authentication and encryption settings - WEP with 802.1x authentication - Cisco LEAP - Settings for short preamble and antenna diversity (Wi-EM only) - Display current authentication, encryption, and network statistics Added support for exposing wireless statistics via RCI Restructured the Web UI into HTML 4.01 compliance Enabled the CLI PING command on this device Added the option of enabling the CLI on a serial port Fixed several issues with alarms including one problem where snmptraps were continuely being sent out Fixed several problems with backup/restore Fixed bug with reporting incorrect ICMP stats Added wireless country support and approval for many European countries and Japan WEP keys are now checked for length Fixed a problem where network links would not come up when connecting to a Leadership Network Hub Fixed several RCI memory leaks Added support for RTS toggle predelay and postdelay On receiving an RCI reboot command, the unit would give an incorrect response Fixed a problem where using raw sockets resulted in lost serial data when sending a NULL character Fixed a problem where RCI over serial would stop accepting data Fixed a problem where the agent IP field in an SNMP trap was incorrect if the unit received its IP address via DHCP Fixed a problem where changing the destination IP address for SNMP traps required a reboot to become effective 82000983_E1 Fixed issue with wireless failing to work properly at cold temperatures. Fixed problem where socket connections to serial were not always draining completely after the socket disconnected (#14000). 82000983_E Initial product release. 82000983_1P Pilot release.