Hi, We use FreeRadius 2.1.9. It works fine, but Macbook user can't connect. I have to activate only TTLS and PEAP in WLAN settings (802.1x) on the macbook, then it works. Do exist any other possibility for MAC user? PLZ help :) Lionne Stangier ---------------------------------------------------------------------------- Lionne-Jeremias Stangier Praktikant system engineer allesklar.com AG turmcenter ? am turm 40 d- 53721 siegburg e-mail: lionne.stangier@meinestadt.de fax: +49 (0) 2241-9253-66 www.allesklar.com www.meinestadt.de - das portal für alle städte deutschlands www.meinestadt.de/mobil - mobile apps von meinestadt.de www.allesklar.de - deutschlands umfangreichster webkatalog www.datingcafe.de ? die testsieger-singlebörse http://blog.meinestadt.de ? der blog von meinestadt.de allesklar.com AG | siegburg | AG siegburg HRB 7031 vorstand: dr. manfred stegger (vors.), peter bettin vorsitzender des aufsichtsrats: dr. herbert groeger
Hi,
We use FreeRadius 2.1.9.
It works fine, but Macbook user can't connect. I have to activate only TTLS and PEAP in WLAN settings (802.1x) on the macbook, then it works.
Do exist any other possibility for MAC user?
by default, OSX has a lot of EAP types enabled...and will try to use them all , in-order....which means a lot of junk EAP attempts - which your FR will reject if it doesnt know - and may confuse the AP/NAS - certainly if you dont allow FreeRADIUS to handle unknown EAP types. if you only support PEAP and TTLS then ensure that your clients are configured correctly. recommend using either the enterprise deployment tool (profile configuration generation tool), an OSX config script, well documented instructions or an 802.1X tool such as XpressConnect from cloudpath. alan
ignore_unknown_eap_types = no
but as the docs clearly state, if its not handled in another module then the request will still get rejected
Thanks, Ok. I need to configure the Mac client or install a 802.1x tool. No other way ... hmm ... ok. lionne
Hi,
Ok. I need to configure the Mac client or install a 802.1x tool. No other way ... hmm ... ok.
umm, the client is set to try all the EAP methods under the sun - starting off with FAST , then LEAP, then PEAP etc.... well, theres nothing a server can do to change that - its totally client related - now, if your AP/NAS has some other thing like EAP fail limit etc then those initial requests and NAKs stack up - it might not even be getting the chance to do what you want. its a bit like saying "my client is set to a static IP address, how do you configure the DHCP server to fix that?" ;-) alan
participants (2)
-
Alan Buxey -
Lionne Stangier