detail logging not right with IPv6 clients

[Alan Buxey]

hi,

believe I have found a small bugette in FreeRADIUS. Although
I'm posting to the list to ensure I'm not just being silly or
if there is another way to get the result.

whilst our config has been tweaked to local requirements, we are
running the pretty much standard detail.log module which
dumps auth log etc into a subdirectory of the radius log directory eg

radacct/127.0.0.1/auth-log-XXXXXXXX  or such


however, this only works when the client is using IPv4.

when the client is using IPv6 then this directory is not made and
therefore no nice detail logs are kept for those things...(well, they
are, but read on......)


( and its not quite true in our case as we ALSO use another detail module
and the buffered-sql virtual server..thanks very much, we are saved. )


however, I'm concerned for those who dont tweak and this 'out of box'
detail.log should work..... obviously, its to do with
the fact it uses %{Client-IP-Address} as part of the detailfile construction
as the logs show:


[auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct//auth-detail-20100914

[reply_log] /var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d expands to /var/log/radius/radacct//reply-detail-20100914

and thus all of the detail logs for ANY IPv6 client get munged into the
top level directory.



alan