Good morning Stefan, perhaps the solution you proposed could work in my case. Could you suggest me the way to check if the lag depends on the DHCP service? Do you know if there is any way to configure the DHCP service timing (we are using freeradius + Chillispot on the server side) so to avoid this case? Thank you! On 12/18/06, Stefan Winter <stefan.winter@restena.lu> wrote:
Good evening,
Good morning to all, I am coordinating a project for installing a wireless network at the Faculty of Statistics of University of Rome. We have been using freeradius with PEAP and EAP-TTLS enabled. All seems to work fine except for the very long authentication times (about one minutes) we are experiencing when using the default Windows XP supplicant. ...
Thanks in advance for any help!
I haven't done any extensive research, but my bundled Intel PRO/Wireless supplicant (comes with Centrino chipsets) gets it done within a few seconds. I believe that the time of issuing the DHCP request after authentication is quite crucial. If it is triggered too early, you hang around in an authenticated-but-not-ready state until the DHCP request times out and is tried again.
Greetings,
Stefan
-- Umberto Ferraro Petrillo PhD Dipartimento di Statistica, Probabilita' e Statistiche Applicate Universita' di Roma -- La Sapienza P.le Aldo Moro, 5 00185 - Rome, Italy phone: +39 06 499 10513 e-mail: Umberto.Ferraro@uniroma1.it