Hello.
When GW
is trying to start a L2F tunnel it asks Radiator for 2 usernames with password.
These usernames are names of NAS and GW, so GW asks them from Radiator in
order to authenticate itself to NAS and in order to authenticate NAS to itself.
After this authentication tunnel will be opened. Here is a GW log when this
authentication does not complete: (interesting that there is no log records in
Raditor's log about asking names "acc" and "acc2").
...
1d04h: L2F: Creating new tunnel for acc2
1d04h: L2F: Tunnel state closed
1d04h: L2F: Got a tunnel named acc2, responding
1d04h: AAA/AUTHEN: create_user (0x27BDC8) user='acc' ruser='' port='' rem_addr='
' authen_type=CHAP service=PPP priv=1
1d04h: AAA/AUTHEN/START (483411013): port='' list='default' action=SENDAUTH serv
ice=PPP
1d04h: AAA/AUTHEN/START (483411013): found list default
1d04h: AAA/AUTHEN (483411013): status = UNKNOWN
1d04h: AAA/AUTHEN/START (483411013): Method=RADIUS
1d04h: RADIUS: SENDPASS not supported (action=4)
1d04h: AAA/AUTHEN (483411013): status = ERROR
1d04h: AAA/AUTHEN/START (483411013): failed to authenticate
...
After this NAS and GW stop trying to establish a tunnel. What could it be?
Mine opinion that Radiator somehow can not process this request at all. But
if I test these names "acc" and "acc2" via radpwtst or via loggin to cisco from
telnet, Radiator works fine (procces my requests).
--
Bye.
Alex S. Burba
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
