Support of Tag 0x00 for Tunnel-Server-Endpoint

[Alan DeKok]

Naoufel wrote:
> To clarify :
> 
>> I'm using free radius 2.1.9 as a client to connect to a
>> distant server (not freeradius). 
> 
> I'm using API for client access not the freeradius as a server

  I have no idea what that means.

>> So, there is no explicit prohibition of use of 0x00 as a Tag value.

  There's also no way of knowing what the *right* behavior is.

>> What we see in freeradius is that this values makes as ignore the value of the atrtribute.
> 
> This means : 
> - if we receive a Tunnel-Server-Endpoint with a Tag 0x01 value and that contains an IP@, the IP is taken into consideration and its value is returned by the API. Applicative layer uses it.
> - But if we receive a Tunnel-Server-Endpoint with a Tag 0x00 value and that contains an IP@, the IP is just ignored, its value is not returned by the API. The call to recv_one_paquet returns an empty Tunnel-Server-Endpoint value

  That looks like what the code is doing.

> The no tag, is may be whell managed at server part, but misused by client part ?

  I have no idea what that means.

  If the client is sending a tag of 0x00 for IP addresses, it's broken.
 Fix the client.  No other client in the world does this.

  Alan DeKok.