hi
sorry, it was my fault, i misread your "XP supplicant" as xsupplicant. :-)
some kind if issue between the Cisco card and xsupplicant? I have
yes, indeed there is. xsupplicant does not seem to support the way the newest drivers handle some packets.
Pardon my RADIUS newbie wording... "all aspects of authentication" is a bit exclusive, isn't it? What I meant to say, is that I don't understand why a wireless device can't just work at the lowest common denominator, and let the supplicant and the authenticator do all of the communication. I understand that there are driver/firmware issues with cards, but why does it have to be this way? Isn't there just an exchange of EAP info?
there is. however, EAP is not data, it is encapsulated in EAPOL which is a protocol using a special ethernet frame type. the card's firmware should explicitly know this new ethernet frame type since otherwise it would just drop it, right from the hardware.
now, once you've changed the firmware of the card, the supplied driver has to provide the necessary API for windows to access to these packets and write them, etc.
since at the beginning there were multiple different drafts of the 802.1X document, some things have changed and are a bit different today. depending on your card and your AP there can be issues...
hey, what's so surprising? don't you remember the times as Cisco wireless cards could not connect to Lucent Access points though both were sold as 802.11 compliant? that's when the WiFi test was born...
greetings artur
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
