I'm certainly open to any others also! Wireless APs (it turns out) are a very inconsistent breed. My intent was, and still is, to do MAC address (only) authentication. Not with EAP, WAP, etc added on...
To that end I've got a Cisco AP 350, Symbol AP4131, 3Com AP8000 an Orinoco AP1000 in house to test. The Orinoco was first: Set up FreeRADIUS to do "user" authentication and created user accounts with the MAC address in the format 111111-222222 - password didn't matter. Point the AP at the IP address of the FreeRADIUS box, created a shared-secret account in clients.conf and we're done. Next comes the 3Com AP8000: Difference is the AP8000 expects the user account to be in the format 1111122222 and the "user's" password to be the same as the MAC address (the user account). The Symbol AP generates an authentication error (on the FreeRADIUS box) but other than that no (zero, nada) traffic goes from it to FreeRADIUS. I'm now into Level-III (maybe level IV) tech support with Symbol to figure out what's the deal. The Cisco AP doesn't do anything. If I configure it to "do" RADIUS authentication NICs will associate with the AP but the AP doesn't pass any traffic on to FreeRADIUS for authentication. I think it must be something to do with it (AP) expecting to also do EAP. I've not got an incident into Cisco yet. Please, someone, tell me how this is supposed to work!!! TIA - Owen [EMAIL PROTECTED] writes: >Hi all, > >Could you please write your freeradius experiences in 802.11 Wireless LAN. > >Can we setup freeradius to allow certain MAC addresses? and Is there >need >for a third party software in the Wireless clients? > >Regards, > >Tamer - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
