CUSTOMER RELEASE NOTES
1/21/09 P/N: 9038177-27
Subject to Change Without Notice
Page: 12
of 28
F0615-O
Firmware Release 6.0.5.1:
The 6.0.5.1 release now supports 25 ACL rules (ACEs) per ACL, total of inbound and outbound, to be mapped
to the user if the AP has Direct Path Forwarding (Local Switching) enabled. There can be more than one ACL,
with 25 ACEs, applied to multiple users on the AP. If an ACL with 26 or more rules is mapped to the user with
Local Switching enabled, the users in the network will not connect or authenticate to that wireless network.
Enterasys Networks recommends creating separate ACL profiles to be used for those users who are
authenticated into the Local Switching VLAN profile.
Resolved an issue with the Web Authentication page and login slowness due to the memory buffer for non-
parsable http requests not being freed.
Resolved a memory leak issue in the TCP machine that caused Netsys crashes. The memory was not freed in
cases where the client attempts to close the tcp connection from its end but we still have some data to send out.
Resolved an issue where certain wireless IP phones would not connect to the AP1002, RBT3K-AG, or
RBT-4102.
Resolved an issue where Radius calling-station-id not sent by the Web-portal functionality.
Resolved an issue where an NMAP scan would cause the web portal page to no longer function.
Resolved an issue where a WebView error was seen for the browser URL reference icon.
Resolved an issue where ACL rules were not applied to a Locally switched user.
Resolved an issue where certain fdb errors were seen on a Mesh AP after it was reset.
Resolved an issue when the login WebAAA page displayed a partial logo or title header.
Resolved an issue where a Bonded Authenticated user would not get an IP address using the TKIP cipher.
Resolved an open endian issue where an ICMP ACL rule (ACE), with either the source or destination IP address
fields and masks configured, will not get applied to an authenticated user with Direct Path Forwarding (Local
Switching) enabled.
Resolved an issue where the ACL Mapping with Local Switching fails after adding the 17th ACL rule.
Firmware Release 6.0.4.4:
Resolved an issue where a bit on the non-mesh supported Access Points could be randomly set, causing the
APs to reset several times.
Resolved an issue where an external antenna attached to the TRPZ-MP-422 Access Point was not transmitting
the configured power.
Resolved an issue for the RBT-8400 where system generated core crash files were truncated and unreadable.
Firmware Release 6.0.4.2:
Added support for the TRPZ-MP-620 Outdoor Access Point. Direct Path Forwarding (Local Switching), Mesh
Services, and Wireless Bridging are only supported on the TRPZ-MP-620 and TRPX-MP-422 Access Points.
The RBT-8400 image is smaller than previous releases due to a shared library format introduced in the 6.0
firmware. Statically linked executables, which called to individual library functions, were replaced with run-time
calls, reducing the total number of individual library routines to be opened, and reducing the overall size of the
firmware required to operate the network switch. This format also increases the amount of memory available for
data transfer and table maintenance.
Resolved the issue where the Static IP configuration and deployment for the AP4102 and AP3000 did not
remain persistent with the AP upon reboot.
Resolved the erroneous message error printed to the CLI when the RBT-8400 reboots with 5.0.12.2:
Bootloader upgrade 5.0.x to 5.0.x needed. (x could be any number)
cp: /boot0/bload: No space left on device
Resolved an issue where the TRPZ-MP-422 Access Point image does not load with the 6.0.x code.
Resolved an issue where the configured APs in a network plan would crash upon RAS firmware upgrade due to
a DNS update entry on the RAS.
Resolved an issue where the Radius CLASS attribute was not sent with stop packets.
Resolved an issue where the RAS spoofed a DNS reply with a 169.254.x.x if the DNS server took more than 3
seconds to respond. Certain Linux and Vista users will drop this packet causing everything to fail
Resolved an issue where the configured APs would crash with various exception messages, including TLB data
miss and sigtrap.
