MikroTik

did not know exactly when this happens. But in WinBox, the "Last Link Down Time" is displayed wrong. It is correct displayed in the Web-Interface.
It display some time in the future, it looks like starttime of WinBox + 30 hours. Uptime itself is correct.

See screenshot.
Does anyone else see this? Would be nice to get the correct value here, so i don't need to grep the info out of the logfiles if i need this.

Router is an CCR1009-8g-1S-1S+ with latest 6.43. But i saw this also in latest 6.42.

Happen to my CCr1009-7G too, everywhere is correct except in winbox, beside link down time the "last link up time" will sometime display the current time instead of the correct one

Happen to my CCr1009-7G too, everywhere is correct except in winbox, beside link down time the "last link up time" will sometime display the current time instead of the correct one[/u]
The same problem in my RB3011UiAS after upgrade to v6.43. Any solution??
Thanks in advance!

I am also having this problem, on RouterBOARD 3011UiAS, running 6.40.9, Firmware 3.41 However I do not believe that this has to do with upgrade version or firmware. I believe that it is the newer versions of winbox.

Winbox 3.11 connected to the same router shows CORRECT dates in "last link up time" and "last link down time"

Winbox 3.17 shows incorrect dates, specifically about 18 hours in the future.

Winbox 3.18 shows incorrect dates as well.

I can confirm that this occurs on the following routers using Winbox 3.17 AND Winbox 3.18.
Note: The strange date behavior is NOT occurring with winbox 3.11, on the versions that it can connect to (pre 6.43).

3011UiAS, running 6.40.9, Firmware 3.41
Power Box Pro (960PGS) running 6.42.7
750UP running 6.42.7
Power Box 750P r2 running 6.43
951-2n running 6.43
2011UiAS-2HnD running 6.43 -- This one is weird. The last link uptime of all active interfaces seems always gets set to the time that winbox connected ...

The incorrect dates appear to be random. Each time winbox connects, they may or may not change to dates ranging from a few hours to a few weeks in the future ... That it to say, one cannot simply calculate the true date.

Kind regards, --

Bump...

Yesterday I got around to upgrading all of the RBs in my previous post to 6.43.4, and a CRS 326 as well, both firmware and packages. Using both winbox 3.17 and 3.18, the "Last Link uptime" of all active interfaces always gets set to the time that winbox connected ... The last link downtime is always blank.

Six different models of RB, and a CRS, all with the same problem. Does anyone know if the next version of Winbox will address this issue? Does anyone know if there is a workaround?

Hi

On Ticket#2018110622004024 I got :

Hello,

Problem is now reported to our development team.

When it will be fixed, then detailed problem description (fix) will be mentioned in RouterOS and/or Winbox changelog.

I reported it as well

Ticket#2018103022005561

Mikrotik support asked me for screenshots and additional details, I gave them screenshots from 3 differnt RBs, and using different versions of Winbox (when possible). Hopefully it will be corrected in the next version of Winbox.

I am also having this issue with my routers.
I have a CCR1009-8G-1S-1S+ 6.43.2

So strange the dates showing in last link down and uptime are seemingly random. For instance the one I am looking at now is 1 month 5 days ahead.
I checked the system clock on both routers, both are "correct" as in the date and time are accurate, but the interface details are completely wrong.

I also notice this on some of my VPN clients. Many show "Last Link Up Time" over a month in the future.

I was able to resolve this on our workstations, it seems to be a difference in how Winbox is writing session files. If you delete the "%userprofile%\appdata\roaming\mikrotik\winbox\sessions" directory, then it all works fine again and correct link down dates are shown. We've confirmed that on two different computers and so far, so good!

I was able to resolve this on our workstations, it seems to be a difference in how Winbox is writing session files. If you delete the "%userprofile%\appdata\roaming\mikrotik\winbox\sessions" directory, then it all works fine again and correct link down dates are shown. We've confirmed that on two different computers and so far, so good!

Thank you, will try this next time

I was able to resolve this on our workstations, it seems to be a difference in how Winbox is writing session files. If you delete the "%userprofile%\appdata\roaming\mikrotik\winbox\sessions" directory, then it all works fine again and correct link down dates are shown. We've confirmed that on two different computers and so far, so good!

I confirm that this works, but only for the first time that winbox is used after the session files are deleted. Once the session data is rewritten by winbox, the next time winbox is opened for that RB, the same problem appears. This may be useful information for the Mikrotik developers, but it's not a usefull workaraound, especially since the session data contains all of the winbox column formatting that I am sure we all painstakingly work on ... I would rather use the terminal to see one erroneous data point, that to lose all of my other winbox formatting ...

I confirm that this works, but only for the first time that winbox is used after the session files are deleted. Once the session data is rewritten by winbox, the next time winbox is opened for that RB, the same problem appears. This may be useful information for the Mikrotik developers, but it's not a usefull workaraound, especially since the session data contains all of the winbox column formatting that I am sure we all painstakingly work on ... I would rather use the terminal to see one erroneous data point, that to lose all of my other winbox formatting ...

I can confirm that too. The same problem, and deleting sessions files works ONLY for the first time. Next login with Winbox - shows the wrong "Last Link Down Time" - there is a logon date and time!
MikroTik team - please repair that problem.

I confirm the problem.

Same here!
RouterOS: 6.44.1
WinBox: 3.17

same here, a real issue when you to need to prove something.

1y passed. Problem still not resolved
RB3011UiAS
ROS 6.44.3 (latest "stable")

Problem persists.
CCR1036-12G-4S
ROS v6,46,5
WinBox v3.22 (64bit)

Проблема до сих пор не решена!!!
The problem is still not resolved !!!

Есть обходной путь решения проблемы, надо переименовать папку сессии, зайти в винбокс и авторизоваться на роутере, закрыть винбокс, удалить новую созданную папку сессии, старую переименовать обратно.
Теперь все работает, но не знаю на сколько долго...

Присоединяюсь к вопросу, имею ту же проблему
I have the same issue

Problem still persist. Please clear it as soon as possible.

In the change log for Version 6.47 (2020-Jun-02 07:38) it states:

*) winbox - fixed dates and times in interface link up/down properties (WinBox v3.24 required);

So ... Supposedly this should be fixed. I have not tested yet because I only use "long term" versions in production routers, whereas 6.47.1 is still only a "stable" version.. But if anyone has time to test this out, please post if the problem was fixed. Kind regards -

upgrade winbox to v3.27 and the problem solved !!!

@doukas, what FW version are you using?