Hi all, I’ve stumbled on an issue with how UM records time/dates in the session logs.
Our main access concentrator (ROS) is running UM. The local time on the ROS is GMT +13 (Pacific/Auckland). when it updates the time from an internet time server (time.nist.gov) ROS automatically adds the time difference and the result is local time. But UM still records the GMT time to all entries.
This has made it fun to track issues on a customers account when they say “it happened around …pm” or “I wasn’t on the internet at 3am!”
Trust me, after explaining the GMT time thing 20 odd times the same question gets difficult.
Hello Best Friend [sergejs]
yes, i leave that problem and Mikrotik maybe not hear about it.
i did try to change to subscribe timezone at +08:00 but same problem, please give us your xperinces.
we had many complain about it from our client.....from time used.....
i believed, you will give as solutions,
drop me any solution about it...
oh yeh...our router as Centalized AAA and Userman with PIII 1Ghz 512RAM 80G HDD routerOS level6 and v....38.
just, time usege is not same as router time...
How to make fix...?
i did try to set time zone on subcriber, but is not goal...
our time is +08:00 from GMT
Unfortunately adjusting the time zone for the subscriber through web interface makes little difference to the time recorded in the session history of sub-customers. That is to say, they all record GMT regardless of subscriber time zone and ROS time zone.
now, i just tell to our customer, the session time on radius is GMT time.
yes, it's simple answer or we are wrong for config our radius server[userman] or RouterOS.
We have checked, if subscriber’s time-zone is changed, time is changed on web interface too.
In other hand, each subcustomer has own time-zone configuration, that migh be changed only by subscriber.
Default time-zone value is +00:00.
Check sub-customer time-zone value, report back with the results.
i leaved this problem, last 2 weeks ago i did do change that point without success. but now is okay i don't know from where that problem has solved. i had reboot 4 days ago and all fine...
that's funny for us...
don't ask why...i don't know......i don't know for solved....
