In article <5.1.0.14.2.20020524100207.02ce3830@mailc>, Chris Parker <[EMAIL PROTECTED]> wrote: >At 08:02 AM 5/24/2002 +0200, PELLE Thierry FTRD/DAC/ISS wrote: >> >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. > >No, it's clear, and that is was it is supposed to do. If you do no specify >a tag to be used, the tag 0x00 is implicitly set. If you want the server >to not send a tag at all under any circumstances, you would edit the >dictionary file to remove the tag flag from the attribute.
I've been thinking about that, and I'm not sure about that. For example, Lucington PM3 boxes have l2tp tunneling support, but I don't think the PM3 supports tagged attributes. Yet you need to send it the Tunnel attributes. If you are serving a PM3 (LAC) and a Cisco box (LNS) of which one doesn't want tags and the other does, you can't just edit the dictionary file - you want both types of behaviour simultaneously. So probably not adding a tag when none is specified is the correct behaviour. But I have read the RFC and I'm still not sure what, if anything, is being said about this. It's ambigious. Mike. -- "Insanity -- a perfectly rational adjustment to an insane world." - R.D. Lang - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
