Hi, Sorry again .. but when you say:
The time is ALWAYS taken from what the NAS sends. Please don't confuse the issue by thinking of it as the time from the RADIUS server. It *might* be the same time. But it is *not* the time taken from the RADIUS server.
When i get an Accounting from NAS from Taiwan i get saved on the FreeRadius from SPAIN the Spanish time not the Time coming from the Taiwan NAS. Example: NAS Taiwan's Time clock is 2018-03-25 07:29:16 am and saved on data base 2018-03-25 00:29:16 am I understand, as you try to explain me (sorry i don't get it), that this exemple should do: NAS Taiwan's Time clock is 2018-03-25 07:29:16 am and saved on data base 2018-03-25 07:29:16 am But it doen not. Thanks -----Mensaje original----- De: Freeradius-Users <freeradius-users-bounces+oscar=jofre.com@lists.freeradius.org> En nombre de Alan DeKok Enviado el: domingo, 25 de marzo de 2018 1:05 Para: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Asunto: Re: Radius acctstarttime On Mar 24, 2018, at 7:34 PM, Oscar Jofre <oscar@jofre.com> wrote:
So if both the NAS and FreeRADIUS use NTP for the correct time, they should have the same time.
Yes.
And when a write on radius comes from that router it saves as 2018-03-25 00:29:16 am ... the time from the centos where is installed freeradius.
Not exactly. The time is ALWAYS taken from what the NAS sends. Please don't confuse the issue by thinking of it as the time from the RADIUS server. It *might* be the same time. But it is *not* the time taken from the RADIUS server.
So if the NAS have an incorrect time (could not sync with NTP) will save an incorrect time on raddact ?
That's what I said. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html