Ben Thompson wrote:
> Nov 14 11:26:12 nassrv3 pppd[15621]: rcvd [CHAP Response id=0x9 
> <4166d4713ef8cec048e88644889a7fbc0000000000000000adcaef9a0709f7576bad0ce28f82ed7e5fb6e8c193a192bb00>,
>  name = "ozw1"]
> Nov 14 11:26:12 nassrv3 pppd[15621]: rc_check_reply: received RADIUS server 
> response with invalid length
> Nov 14 11:26:12 nassrv3 pppd[15621]: rc_avpair_gen: received attribute with 
> invalid length

  Is the packet OK, or is it a bug in the radius client code?

> Here is a packet capture showing the radius conversation :-
> 
> 11:26:12.567346 IP vpn.york.ac.uk.33286 > nasaaa2.york.ac.uk.radius: RADIUS, 
> Access Request (1), id: 0xc1 length: 140
> 11:26:12.568107 IP nasaaa2.york.ac.uk.radius > vpn.york.ac.uk.33286: RADIUS, 
> Access Accept (2), id: 0xc1 length: 179
> 11:26:12.568122 IP vpn.york.ac.uk > nasaaa2.york.ac.uk: ICMP vpn.york.ac.uk 
> udp port 33286 unreachable, length 215

  That would suggest that the VPN server is severely broken.  i.e. it
sends a packet, and then *stops* listening for a response.  Is there a
firewall on the VPN server that blocks RADIUS traffic?

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to