MS-CHAP-Error

[A.L.M.Buxey at lboro.ac.uk]

Hi,

> Sending Access-Request of id 7 to 192.168.29.34 port 1812
>         Service-Type = Framed-User
>         Framed-Protocol = PPP
>         User-Name = "test"
>         MS-CHAP-Challenge = 0xSNIP
>         MS-CHAP2-Response = 0xSNIP
>         Calling-Station-Id = 192.168.55.55
>         NAS-IP-Address = 192.168.54.54
>         NAS-Port = 0
>         Proxy-State = 0x3633
> --- Walking the entire request list ---
> Waking up in 6 seconds...
> rad_recv: Access-Reject packet from host 192.168.29.34:1812, id=7, length=46
>         Proxy-State = 0x3633
>         MS-CHAP-Error = "\000E=648 R=0 V=3"
>
> ...however FreeRadius obeys the RFCs, and doesn't proxy the MS-CHAP-Error 
> packet back to the radius client (pppd "radius.so" plugin) so my patches to 
> pppd are unable to act on the error code.

how about using ulang to check for the MS-CHAP-Error - and if that code
exists, create a new attribute that WILL be sent back to the radius client.
...one on which other bits of code could act.

alan