I havent noticed this in versions before 7.2.rc5 on my HAP AC2. The sort by date doesnt work in descending order. There appears to be a logic error thinking that log event 101 is newer than log event 194
Are there between event 101 and 194 indications of time change, like NTP or so ?
I hope the event numbering remains chronological, regardless what happens.
I am trying to derive some logic but it doesn’t make sense indeed …
If column Time is used, it should sort correctly whatever there is behind the scenes.
Have you reported this to support@mikrotik.com ?
Adding: are you seeing the same behavior in Winbox ? Could be Webfig specific, that’s why I ask.
There are no NTP events. The issue appears to be a logic error with the sorting descending and how it interprets the 24 hour times, ie it can’t handle whether 00-1200hours is newer or older than 1300-23:99 hours.
Sorting any other way works a treat. Sorting by Time ascending works fine etc.
Just reported it here so someone might incorporate a fix into the next build. Didn’t need any support.
Test it on new release:
http://forum.mikrotik.com/t/v7-2rc6-and-v7-2rc7-is-released/156927/1
Support does not read this forum.
Best to report to support@mikrotik.com.
What happens if you sort by # instead of date?