User`s guide

RN-WIFLYCR-UG
www.rovingnetworks.com Version 1.2r 4/30/13 page 112
• Deprecated the wps command.
F.2.2 Bug Fixes
• Fixed a bug wherein the UART would occasionally lock up upon performing the
factory RESET command and while telnet session was in progress.
• Fixed a bug in soft AP mode wherein the module would close the TCP connection
upon another client being deauthorized.
• Fixed an issue with the link monitor in AP mode to correctly age out stale clients.
• Fixed an issue that would cause the module to crash due to a high-speed optimi-
zation error.
F.3 VERSION 2.36/2.45 9/14/2012
• Firmware versions 2.36 and 2.45 are being shipped together. Version 2.36 sup-
ports ad hoc mode, while version 2.45 supports soft AP mode. All modules
shipped with these firmware versions will run version 2.36 by default to maintain
backward compatibility with previous firmware versions.
You can change the firmware image using the boot image <value> command.
After you change the boot image, you MUST reset the module back to the factory
defaults using the factory RESET and reboot commands.
- Wifly_EZX-236.img—Ad hoc mode firmware for RN-171
Wifly_GSX-236.img—Ad hoc mode firmware for RN-131
- Wifly_EZX-245.img—Soft AP mode for RN-171
Wifly_GSX-245.img—Soft AP mode for RN-131
• In firmware version 2.36 (ad hoc version), the auto join feature is enabled to main-
tain backwards compatibility. In version 2.45, auto join is disabled and you must
explicitly enable auto join mode using the set wlan join 1 command.
• The firmware now supports parity with the set uart flow command.
• Added the i flag to the set wlan channel command, which changes the channel
immediately. You can use this feature to go into AP mode without having to reboot
or save the settings.
• In AP mode, de-authentication with the link monitor closes the TCP connection,
flushes the UART buffer, and tries to clear stuck RTS flow control.
• In some cases flow control can get “stuck,” e.g., during a tcp_close or de-authen-
tication in which the UART cannot transmit a TCP packet and is holding it. Added
a fix to attempt to clear the buffer.
• In previous firmware, the associated status is always set even if no clients are
joined. In version 2.45, the red LED correctly shows the status if there are no
devices joined.
If you use ALTERNATE IO for associated, it is high if there are 1 or
more clients, and low if there are no clients.
• In AP mode, the module supports 7 connections (DHCP and AP).
• Fixed an issue with the ping command.
F.4 VERSION 2.30 10/26/2011
• Added support for incorrect WPA modes, namely WAPv1 with AES encryption