Additionally
Sending Access-Challenge of id 134 to 192.168.0.253:1072
that is the IP of my Wireless AccessPoint as the laptop does not have an IP yet as it is set to dhcp.
I dont think this is important however.
Regards Dave
----- Original Message ----- From: "Alan DeKok" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 19, 2004 5:02 PM
Subject: Re: error authenticating wireless user
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:I have it setup to use peap and all the configurations seem correct. I have the shared secret set in the clients.conf for the AP and the same key set on the Radius section along with the IP of the server on the AP.
Yup. The debug log shows that everything is configured correctly.
Notice that for some reason the password is not there ?
It's using EAP, which doesn't include the password.
...Sending Access-Challenge of id 134 to 192.168.0.253:1072
What's happening is that the server is going through the EAP conversation, and at some point, the laptop stops responding to it. There's not much you can do to the server to solve that problem.
Alan DEKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
