There appears to be a bug in radclient
When sending multiple chap auth requests
only the first packet is valid.
When I use radclient to
to send a single packet but
use the command line to send it twice
no problem.
I think it might have something to do
with where the AUTH_CHALLENGE
gets stored in the packet. This place
must change on each packet when
raclient is called using -c
whereas it shouldn't or something
like that.
Anyway its not really an issue
but some of you might want to note
this before you test any CHAP packets
on your own setups.
Rob
[root@skrimir bin]# ./radclient -c 2 -f dchaptest2 195.146.169.246:1812 auth
secret_key
CHAP ENCODE Password: |testing2|
CHAP ENCODE Password length: |8|
CHAP ENCODE ID: |dc|
Using AUTH_CHALLENGE
Received response ID 221, code 2, length = 26
Framed-Protocol = MPP
Received response ID 222, code 3, length = 20
[root@skrimir bin]# ./radclient -f dchaptest2 195.146.169.246:1812 auth
secret_key ; ./radclient -f dcha
ptest2 195.146.169.246:1812 auth secret_key
CHAP ENCODE Password: |testing2|
CHAP ENCODE Password length: |8|
CHAP ENCODE ID: |dd|
Using AUTH_CHALLENGE
Received response ID 222, code 2, length = 26
Framed-Protocol = MPP
CHAP ENCODE Password: |testing2|
CHAP ENCODE Password length: |8|
CHAP ENCODE ID: |de|
Using AUTH_CHALLENGE
Received response ID 223, code 2, length = 26
Framed-Protocol = MPP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
