I am running WPA_SUPPLICANT 0.6.10. I am testing on a network with WPA/PSK security. However, someone else is testing with a different network overlaid on mine that uses a Radius server. That network uses the same APs but a different SSID. The APs are Cisco, AirLAN (or something like that). At the moment, my code is not setup to handle that kind of security. However, I am seeing a line 'proto=3DRSN' that is being added to most/all network sections of the supplicant configuration file, even when my UI code hasn't instructed the supplicant to update the file. Needless to say, this is causing hopping to fail due to security authentication failure. I don't understand why, but I am able to initially associate with an AP on the network, I just can't hop. Is this a known problem with this release? Is there something that I can do to supress this behavior? Thank you, Chuck Crisler -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
