Ahhh, Thank you Alan. That clarifies things. :-) Have a good weekend! Stefan Paetow Federated Roaming Technical Specialist eduroam(UK), Jisc email/teams: stefan.paetow@jisc.ac.uk gpg: 0x3FCE5142 For eduroam support, please contact the eduroam team via help@jisc.ac.uk and mark it for eduroam’s attention. On Wednesdays and Fridays, I am not available between 12:00 and 15:00. jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: 4 Portwall Lane, Bristol, BS1 6NB Tel: 020 3697 5800. On 29/09/2023, 15:04, "Alan DeKok" <aland@deployingradius.com <mailto:aland@deployingradius.com>> wrote: On Sep 29, 2023, at 9:58 AM, Stefan Paetow via Freeradius-Users <freeradius-users@lists.freeradius.org <mailto:freeradius-users@lists.freeradius.org>> wrote:
I know this is probably something really obvious but… Does FreeRADIUS log in UTC or the local timezone? Is there anything specific in terms of settings (in radiusd.conf) to make FreeRADIUS log in UTC by default if it does not?
It logs in the local time zone. This can't be changed.
I’ve looked at the date {} module and I note that both the ‘date’ and the ‘wispr2date’ xlats have the option to output things in UTC… would that be the only thing where this can be tweaked?
Yes. We're looking at fixing this in v4. RFC3339 defines a better format for dates which is much more correct, and avoids all localization issues. It may also be useful to log times as numbers, which avoids a lot of issues too. Alan DeKk.