I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?I installed 5.2 on a pppoe (bras) mk router.
Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny
So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!
It seems it's like starting timer from -40seconds
I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?I installed 5.2 on a pppoe (bras) mk router.
Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny
So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!
It seems it's like starting timer from -40seconds
Please describe this problem in more details.There is some serious issue with pppoe connectivity in 5.2 & 4.17.
I downgraded to 5.0rc4 all issue solved but rc4 UM is not stable
BTW, I netinstalled 5.2 on a RB433 and at two RB450 because they had 0.3 ... 0.5% badblocks with the built in ROS (4.11 I guess). Even formatted NAND from boot menu (via RS232 console) to "zero" this readings.bad blocks 4.x,5.2> 0% ........ install RouterOS 5.3 (distib. 17.05.) bad blocks 4,2% ... RB433UAH
You are absolutely correct. When the router reached a higher uptime no more of this issue.I was not able to repeat it. What architecture is the PPPoE server and client? Any specific configuration?I installed 5.2 on a pppoe (bras) mk router.
Till now I see a bug. in PPP, active connection you can see new connecting pppoe client uptime starts from 39seconds and starts decreasing till reaching 0, then starts increasing! So funny
So it's user "yyy" connect. you can see it's alive for 39, 38, 37, 36, .... , 0 , 1, 2 ,.... uptime!
It seems it's like starting timer from -40seconds
I have seen a similar thing with OVPN uptime. I was able to make a screenshot and send it to support with supout. The issue is that the counter doesn't start from 0, but instead it will count from the current uptime value of ROS ... So In my case it said that the uptime was 19hrs ... I guess if the uptime value is large enough and the counter's underlying variable is unsigned, I can see this causing a backward count, but the initial value would be something random.