first authentification fail second one works
Hello Guys I'm writing from Germany. I write my Bachelor Thesis about the Freeradius Projekt. I have a problem and i can't find a solution for it, at the internet by myself. I'm using version 2.1.9 of freeradius and everything works fine with the authentifications agains my Freeradius server, if I'm logged in at the system (Mac OSX, Linux and Windows) But I want to perform my authentifications while the system is currently booting because i use a LDAP Directory Server and i can't login against the LDAP Server if i haven't got a running Network-Connection (i will get the Connection if the 802.1X Authentification is successful. So i use wpa supplicant on Linux and w2secure on Windows to perform the Authentification while my system boots. But the debug mode tells me, at the first authentification test, that i'm running in a access-challenge (no reasons were given). Now, if i wait one minute and do nothing while waiting this time, i get a access-accept packet. Can you tell me why this happens and what can i do, that the authentification works with the first run while the system is still booting and so i could login to my operating system. I'm looking forword to hear from you Yours Markus rslautern 3724
Markus Burghart wrote:
But I want to perform my authentifications while the system is currently booting because i use a LDAP Directory Server and i can't login against the LDAP Server if i haven't got a running Network-Connection (i will get the Connection if the 802.1X Authentification is successful. So i use wpa supplicant on Linux and w2secure on Windows to perform the Authentification while my system boots.
That should work.
But the debug mode tells me, at the first authentification test, that i'm running in a access-challenge (no reasons were given). Now, if i wait one minute and do nothing while waiting this time, i get a access-accept packet.
All EAP / 802.1X is driven by the client PC. If it stops at Access-Challenge, it's because the client PC stops.
Can you tell me why this happens and what can i do, that the authentification works with the first run while the system is still booting and so i could login to my operating system.
Fix the client PC to keep going. Alan DeKok.
Am 07.01.2011 13:52, schrieb Alan DeKok:
Markus Burghart wrote:
But I want to perform my authentifications while the system is currently booting because i use a LDAP Directory Server and i can't login against the LDAP Server if i haven't got a running Network-Connection (i will get the Connection if the 802.1X Authentification is successful. So i use wpa supplicant on Linux and w2secure on Windows to perform the Authentification while my system boots. That should work.
But the debug mode tells me, at the first authentification test, that i'm running in a access-challenge (no reasons were given). Now, if i wait one minute and do nothing while waiting this time, i get a access-accept packet. All EAP / 802.1X is driven by the client PC. If it stops at Access-Challenge, it's because the client PC stops.
Can you tell me why this happens and what can i do, that the authentification works with the first run while the system is still booting and so i could login to my operating system. Fix the client PC to keep going.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Thank you Alan fpr your Statements The problem is that, this fact happens on Linux and Windows clients and i don't know why and i don't know how to fix it. The curious thing on that phenomenon is that the second trying works fine and so i thought i could be sure that everything on the client is all right. In an other case the second Authentification would not work too. Or is this wrong?
Markus
participants (2)
-
Alan DeKok -
Markus Burghart