Re: Failing to authenticate using FreeRadius(in OpenBSD) + XP as a client +Linksys AP (WRT54v2.2) using peap
with the modified 'users' file also there is no luck. the problem remains the same. The 'Code: Access-challenge (11)' frame from server to the client is showing 'Checksum: 0x921e [incorrect, should be 0x206c]' error. please find the ethereal log as attached as 'eap-failure1'. regards, Venkat ----- Original Message ----- From: Maurizio Cimaschi <mauri@unixrulez.org> To: Venkata LK Mula <vlkmula@saitechnology.com> Cc: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Failing to authenticate using FreeRadius(in OpenBSD) + XP as a client +Linksys AP (WRT54v2.2) using peap Date: Fri, 15 Aug 2008 23:38:19 +0200
Venkata LK Mula wrote:
We are authenticating the clients via 'users' file.
In your "users" configuration file user "test100" (the one that log files are referring to) is
"test100" Auth-Type := EAP Cleartext-Password == "venkat", Tunnel-Type = 13, Tunnel-Medium-Type = 6, Tunnel-Private-Group-Id = 100, Reply-Message = "Hello 100, %u", Fall-Through = No
I would modify it in this way
test100 User-Password == "venkat", Tunnel-Type = 13, Tunnel-Medium-Type = 6, Tunnel-Private-Group-Id = 100, Reply-Message = "Hello 100, %u", Fall-Through = No
Bye.
1. /usr/local/etc/raddb/sites-enabled 2. /usr/local/etc/raddb/sites-available
Usually, in sites-enabled there shoiuld be link to sites-available.
Venkata LK Mula wrote:
The 'Code: Access-challenge (11)' frame from server to the client is showing 'Checksum: 0x921e [incorrect, should be 0x206c]' error. please find the ethereal log as attached as 'eap-failure1'.
All the packets from your server have that problems; so it's probably a bug in ethereal, because the IP stack of the AP should have discarded those packets.
Maurizio Cimaschi wrote:
Venkata LK Mula wrote:
The 'Code: Access-challenge (11)' frame from server to the client is showing 'Checksum: 0x921e [incorrect, should be 0x206c]' error. please find the ethereal log as attached as 'eap-failure1'.
All the packets from your server have that problems; so it's probably a bug in ethereal, because the IP stack of the AP should have discarded those packets.
No. Modern systems often offload packet checksum calculations to the hardware, which "fixes" the packets before they're sent on the wire. Ethereal on the *local* machine will often show the wrong checksums, because they haven't been calculated yet. In recent versions of Wireshark, just click on the offending packet. It will show that the checksum is incorrect, and will display a message explaining why. Please don't give *wrong* advice. It doesn't help anyone. Alan DeKok.
participants (3)
-
Alan DeKok -
Maurizio Cimaschi -
Venkata LK Mula