I am going to make a couple of assumptions. First, I am going to assume
that you are either using WPA, or WPA 2. (I am fairly sure the bug
doesn't exist for dynamic WEP.)
There is a sequence number that is used in WPA to help it sync up the
per-packet keys. According to the standards, this valu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any details you'd like to share would be appreciated, as it may save us
some time in trying to get this fixed with Enterasys. I'm just glad to
hear we're not alone. :)
Our "standard" laptop that we suggested to students was the Latitude
D620, so we'r
We're experiencing similar problems with the D620 and that chipset in a
Nortel(Trapeze) environment. We haven't been able to rectify the
problem in windows and we can't get Fedora Core 5 linux to work with it
at all which compounds the problem since we have a dual boot laptop
program. We have had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We're seeing problems with Intel 3945 A/B/G chipsets and our new
Enterasys/Trapeze wireless switch gear. The clients authenticate fine
against RADIUS, but claim that they're unable to connect to the network.
If we connect through one of our legacy Pr
We have an issue with Macintosh OS 10.3.9 and 10.4.7 wireless clients
not roaming between APs on a single Cisco 4402 LWAPP controller with
current firmware. APs have the same SSID and authentication
encryption. We are using WPA, 802.1x EAP-TTLS/PAP and the Macintosh
native client. The clie
