Hi, > 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?
Well, this is almost exclusively a client-side issue. From FreeRADIUS perspective, the job's done as soon as the authentication succeeded. The issue is that the client may try to ask for an IP address before the port is actually opened, and I don't know how to influence timing on an (XP?) client. The only option I see here is for chillispot: it might act a bit more gratious when receiving a DHCP request but the port has just not been opened - it might let this request through anyways. Or log it, and only answer to it after it has opened the port. In any case nothing where the freeradius-users mailing list could help you, sorry. Stefan -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: [EMAIL PROTECTED] Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
pgp1cLiALjzn4.pgp
Description: PGP signature
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
