6.38.1 pppoe link up/down time wrong

RouterOS General
1

Hi All,

Has anyone else noticed anything like this?

On a MikroTik hAP running 6.38.1, I noticed that its web user interface shows the link up/down times incorrectly:
Last Link Down Time Sep/04/2059 12:37:57
Last Link Up Time Sep/04/2059 12:37:58
Link Downs 33
Uptime 00:24:19

Whereas, times from the CLI are fine:
/interface> /interface print detail where name=“pppoe-adsl-1”
Flags: D - dynamic, X - disabled, R - running, S - slave
0 R name=“pppoe-adsl-1” type=“pppoe-out” mtu=1460 actual-mtu=1460 fast-path=yes last-link-down-time=feb/04/2017 16:57:09 last-link-up-time=feb/04/2017 16:57:10 link-downs=33

Nothing serious, but would be nice to see this addressed in a future release if it is indeed a bug.

2

Nothing to be worried about and sometimes it happens.

3

I’m seeing the same thing through webfig on my hAP AC Lite. It’s not just pppoe but every kind of link status date / time stamp.

4

Not sure if related but is your “/system clock print” correct?

5

Yes… mine is. It’s kept up to date from an SNTP server.

6

I observed the same behaviour on two different routers (750GL and 751G-2HnD), both running the current bugfix version 6.37.4.

7

bump

This is still happening on 6.43.4 (RB435G). Does anyone have a solution?

8

It started happening to me (951G-2HnD, 941-2nD) on the latest stable ROS 6.45.1. Ethernet and ppp links.

WinBox (3.19) Console - correct:
last-link-down-time=jul/08/2019 12:31:21

WinBox (3.19) Interface List - wrong:
Last Link Down Time: Jul/14/2019 09:44:52

Today is Jul/08.

Mikrotik seriously, are you drunk?

9

Interesting.

I just checked the interfaces in my hAP AC Lite running 6.45.1 through Webfig and they’re all fine.

10

I had may be the same issue last week or two. 951G-2HnD and hAP ac lite (6.44) had lost internet connection and was rebooted manually by users.
I found this in hAP logs:

Jul/12/2019 07:37:24 wireless,info 90:A4:DE:EC:9D:B1@wlan1: disconnected, received disassoc: sending station leaving (8)
Jul/12/2019 10:04:30 wireless,info 3C:F7:A4:ED:E4:29@wlan1: connected, signal strength -87
Jul/12/2019 10:04:35 wireless,info 3C:F7:A4:ED:E4:29@wlan1: disconnected, unicast key exchange timeout
Jul/12/2019 10:09:26 wireless,info 3C:F7:A4:ED:E4:29@wlan1: connected, signal strength -86
Jul/12/2019 10:09:31 wireless,info 3C:F7:A4:ED:E4:29@wlan1: disconnected, unicast key exchange timeout
Jul/12/2019 10:09:59 wireless,info 3C:F7:A4:ED:E4:29@wlan1: connected, signal strength -86
Jul/12/2019 10:10:04 wireless,info 3C:F7:A4:ED:E4:29@wlan1: disconnected, extensive data loss
Jul/12/2019 10:14:47 wireless,info 3C:F7:A4:ED:E4:29@wlan1: connected, signal strength -88
Jul/12/2019 10:14:52 wireless,info 3C:F7:A4:ED:E4:29@wlan1: disconnected, unicast key exchange timeout
Jul/11/2019 17:35:21 system,error,critical router was rebooted without proper shutdown
Jul/11/2019 17:35:24 pppoe,ppp,info pppoe-dom.ru: initializing…
Jul/11/2019 17:35:24 pppoe,ppp,info pppoe-dom.ru: connecting…
Jul/11/2019 17:35:29 bridge,info hardware offloading activated on bridge “bridge” ports: ether2-master
Jul/11/2019 17:35:29 bridge,info hardware offloading activated on bridge “bridge” ports: ether3
Jul/11/2019 17:35:29 pppoe,ppp,info pppoe-dom.ru: terminating…
Jul/11/2019 17:35:29 pppoe,ppp,info pppoe-dom.ru: disconnected
Jul/11/2019 17:35:29 pppoe,ppp,info pppoe-dom.ru: initializing…
Jul/11/2019 17:35:29 pppoe,ppp,info pppoe-dom.ru: connecting…
Jul/11/2019 17:35:29 bridge,info hardware offloading activated on bridge “bridge” ports: ether4

“Jul/11/2019 17:35:21” was real local time at reboot moment. Any ideas what has happen?
It seems that wrong time was the reason of their zombie mode. Clock settings was default.

11

Hi Mikrotik team,
still have same issue:

pr detail where name="l2tp-out2"
Flags: D - dynamic, X - disabled, R - running, S - slave 
 0  R  name="l2tp-out2" type="l2tp-out" mtu=1430 actual-mtu=1430 last-link-down-time=oct/01/2019 10:36:48 last-link-up-time=oct/01/2019 10:36:49 link-downs=1

On Winbox: Oct/02/2019 02:50:51 in the future!!?!!

12

Ip cloud update time checked?
System clock time zone auto detect checked ?
RouterOS version?
Winbox Version ?

13

No need to ask for that extra info, it is a well known bug and apparently low-priority to fix.

14

.

IP cloud update time checked? Disabled at all
System clock time zone auto detect checked ? Yes, checked. Tried to disable, same result.
RouterOS version? ROS 6.45.6
Winbox Version ? Version 3.19 or 3.17

15

Enable ip cloud time update…

16

I think it has something to do with Winbox. Everything looks fine on the Mikrotik Android client

17

Yes, it is a well known bug in winbox.
It appears it can sometimes be fixed by deleting the session (.viw) file but I have not observed that.

18

Why? This solved for you?
Enabled, not solved.

19

Solved!

Use new name in “Session” field on WINBOX, this make new .viw file and seems to work…