Release Notes PN 93000530_G Digi Connect Wi-ME 82000977_G EOS March 15, 2006 INTRODUCTION This is a production release of firmware for the Digi Connect Wi-ME. SUPPORTED PRODUCTS Digi Connect Wi-ME ENHANCEMENTS Support for the Ekahau Real Time Location System. Configurable RealPort keepalive. Increased network stack configurability. Various command line improvements, see UI CHANGES later in this document. BUG FIXES Wireless - WEP support now works properly when in wireless ad-hoc mode. - Default wireless transmit power is now maximum (16 dbm). - SSID matching improved in environments with a large number of access points. It is now possible to upgrade the firmware with files that contain a '$' in their filename. KNOWN ISSUES 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 upgrade the firmware on a unit which has password authentication enabled, this release requires one to disable passwords during the time period of the firmware upgrade. If the standard web service (HTTP) is disabled, the encrypted web service (HTTPS) stops operating. They will be made independently selectable in a future release. In order to clear the persistent storage from the CLI one can execute the "boot action=factory" command. The only web accessible method for clearing the storage is available via the reset functionality in the administrative pages at "admin/factory_defaults.htm". 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 UI CHANGES Telnet The "send" command has been added which allows the user to send telnet special character sequences when connected using the telnet client. syntax: send [option] options: ao {Send telnet abort output} ayt {Send telnet 'Are You There'} brk {Send telnet break} ec {Send telnet erase character} el {Send telnet erase line} escape {Send current escape character} ga {Send telnet 'Go Ahead' sequence} ip {Send telnet interrupt process} nop {Send telnet 'No operation'} synch {Perform telnet 'Synch operation'} ----- RLogin The "rlogin" command has been added to allow rlogin connections to remote hosts. ----- Network Options The "set net" command has changed in several ways. The "garbage_byte" and "override_dhcp" TCP keepalive options have been removed. The following options have been added: dns1: dns2: Allows the user to specify the IP address of up to two Domain Name Servers for name lookup. rto_min: Allows the user to specify a lower threshold for the TCP retransmission sliding window calculation. Choosing an value lower than the default of 1000 ms may assist in achieving improved latency performance when retransmissions occur. rto_max: Allows the user to specify the maximum retransmit before the TCP connection is terminated. arp_ttl: Allows the user to specify the amount of time that an ARP entry remains in the network ARP cache. garp: Allows the user to specify how often the unit will announce its MAC address on the network using a "Gratuitous ARP" message. ----- Display command There are a few new network related "display" commands. display sockets: Displays information on how socket resources are being used by the system. display tcp: display udp: Displays information about pending and current connections for TCP or UDP respectively.. display netdevice: Displays the network devices present in the system. ----- Delayed ACK A new option has been added to the "set service" command called "delayed_ack". This allows the user to configure how long the TCP stack will wait for data on which to place the ACK flag before sending a packet with no payload and the ACK flag set. ----- RealPort Keepalive The RealPort protocol has an optional mechanism that uses an internal "keepalive" packet to cause periodic guaranteed traffic on a link. This packet however may cause issues in environments that are metered for traffic or do not require this type of mechanism. The "set realport" command can be used to turn off this behavior with "set realport keepalive=off". ----- Ekahau Real Time Location System set ekahau Purpose Configures Ekahau Client device-location software in a Digi Connect wireless device. The Ekahau Client featue provides integreated support for Ekahau's Wi-Fi device-location solution. Ekahau offers a complete access point vendor-independent real-time location system for wireless LAN devices that is capable of pinpointing wireless LAN devices such as the Digi Connect products, laptops, PDAs, or other intelligent Wi-Fi enabled devices. The solution provides floor-, room- and door-level accuracy of up to 3.5 ft (1 m). The patented Ekahau positioning technology is based on simple signal-strength calibration maps, and enables customers to fully leverage an existing wireless LAN infrastructure without any need for propriertary hardware components. Please visit www.ekahau.com for additional information, including free evaluation licenses for the Ekahau Positioning Engine and Ekahau Site Survey software products. Required permissions: For Digi Connect products with two or more users, to use this command, permissions must be set to one of the following: For a user to display Ekahau client settings: set permissions s-ekahau=read For a user to display and set Ekahau client settings: set permissions s-ekahau=rw Syntax set ekahau [state={on|off}] [id=device id] [poll_rate=seconds] ] [protocol={tcp|udp}] [port=port] [server={hostname|ip address}] [password=string] [name=string] Options state={on|off} Determines whether the Ekahau Client feature is enabled or disabled. The "id," "name," and "server" values must be set before you can set "state" to "on." id=device id A numeric identifier for the Digi Connect device, used internally by the Ekahau Positioning Engine for device tracking over time. This identifier should be unique for each Digi device being located on the network. It must be configured before the device will allow the "state" option to be set to "on." poll_rate=seconds The time in seconds between each scan or wireless access points and communication with the server. Once the Ekahau Client is enabled ("state=on"), every time the Digi Connect device scans the network, it is essentially disassociated with the access point (AP) providing its network connectivity. In addition, during the time, or scanning interval, set by the "poll_rate" option, it will not be receiving or transmitting wireless packets. This could lead to packet loss. Set the "poll_rate" as slow as acceptable in the application where the Digi Connect product is being used. The default is five seconds. protocol={tcp|udp} Specifies whether to use TCP or UDP as the network transport. The default is "tcp." port=port The network port to communicate on. In the default Ekahau configuration, port 8548 is used for TCP, and port 8549 for UDP. This setting must be configured before the device will allow "state" to be set to "on." server={hostname|ip address} The hostname or IP address of the Ekahau Positioning Engine. The maximum length of this option is 50 characters. password=password A password to authenticate with the server. The maximum length of this option is 50 characters. The default for the Ekahau Positioning Engine is 'Llama' name=device name A descriptive name to identify the Digi Connect device to users. The maximum length of this option is 50 characters. This name must be configured before the device will allow "state" to be set to "on." Examples Set identifiers #> set ekahau id=1 server=myepe.domain.com name="Tracked Device 1" Enable Ekahu Client #> set ekahau state=on DOCUMENTATION ERRATA Password authentication can be enabled in this release, but authentication is OFF BY DEFAULT. A security screen has been added to the user interface to allow one to enable username and password authentication. When password checking is enabled, the user will be challenged when accessing the initial screen of the UI or if the user uses the Digi Device Discovery tool. 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-ME 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-ME 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 The Digi Connect Wi-ME firmware has the ability for an embedded host system to both soft reset the unit as well as reset the unit to its factory defaults. Both functions may be invoked via manipulation of pin 20 on the Wi-ME module's header: * If the module is running (i.e. more than a few seconds after power on), holding pin 20 low for a second and then raising it will soft reset the unit * If pin 20 is held low for more than 10 seconds from the power on or release from hard reset of the unit, and then raised, it will reset the unit to its factory default state In either case, the action takes effect when the pin is raised (reset released). On the development board placing a jumper across pins 2 and 3 of jumper block P12 will cause pin 20 to be low. ADDITIONAL INFORMATION The configuration save and restore tools will save every configurable parameter (including IP configuration) except for those 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 82000977_F 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). 82000977_E Initial production release. 82000977_1P Pilot release.