Linelog - timestamps

Arran Cudbard-Bell a.cudbardb at
Thu Jun 23 15:46:54 CEST 2016

> On 23 Jun 2016, at 09:36, Alan DeKok <aland at> wrote:
> On Jun 22, 2016, at 9:13 PM, Pshem Kowalczyk <pshem.k at> wrote:
>> We've started using the linelog module to record various events that happen
>> within the radius system. All of our linelog entries start with "%t" to
>> denote the time of the event. During one of the troubleshooting sessions
>> we've discovered that the entries don't necessarily end up in the order we
>> expected them to.
>  The entries are written sequentially, so they are in time order.
>> Finally we realised that the "%t" is the time the request
>> hits radius and not when the linelog entry is processed. In our case (we
>> proxy all requests) that actually matters, since the home servers can take
>> time to respond. I had a look through the dictionaries and
>> run-time-variables but can't find 'current timestamp', is it actually
>> available?
>  For various reasons.. no.
>  If your proxies take more than a second to respond, there's something seriously broken with them.  That should be fixed rather than poking FreeRADIUS to have more up to date timestamps.

There's no cost to us though as we get packet timestamps from the kernel as part of recvmsg.


Arran Cudbard-Bell <a.cudbardb at>
FreeRADIUS Development Team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <>

More information about the Freeradius-Users mailing list