>> - When I try to transmit untagged Tunnel AVP the packet
>> received has a bad length (it seems that the FreeRADIUS create a packet
>> as if the tag is present) ;
>Yeah, well that's what the RFC says to do. If the tag is not present, a
>tag of '0' is assumed.
The RFC says that the tag IS present if the value of the TAG field is less or equal to 0x1F,
else the first byte of the "string" field is the TAG field.
>What is reporting the packet having a bad length?
Well for instance, if I try to transmit a "Tunnel-Client-Endpoint" AVP with no TAG and value say 10.0.0.1,
the size of the packet must be increased by 1(TYPE)+1(LENGTH)+8(STRING SIZE)=10 bytes. Despites, FreeRadius trasmit a paquet
with 11 bytes = 10bytes(OK)+1(Assumed TAG field)...
I will try to make a capture of frame if that's not clear.
>> - When radiusd received an accounting-stop packet there
>> is a "segmentation fault".
>This should create a 'core' file that you can back-trace with gdb. Or,
>you could run radiusd from inside gdb and issue the 'bt' ( backtrace )
>command when/if it crashes.
Well, even if FreeRadius is Beta I'm no so skilled to understand "core" files... gdb is a bit mysterious for me...
Thierry
