ROS 6.x Simple Queue Time Match Problem.

RouterOS General
1

Greetings, I have a simple queue that matchs by time, it works fine on ROS 5.x and prior. After upgrade to 6.x, it shows as invalid.
I did some tests, and realized that it accept the end time after 14h or plus. Any value above this it gets invalid. Here some screenshots showing the bug.

All tests where done on the same routerboard, one omnitik, with routeros 6.1.
The same rule works fine on the same routerboad with the ros 5.25.

Tested on ROS 6.0 and 6.1

Thanks in adivice.


How to Reproduce the bug:

/queue simple
add name=teste-time1 disabled=no target=0.0.0.0/0 max-limit=100M/100M time=0s-6h,sun,mon,tue,thu,wed,fri,sat
add name=teste-time2 disabled=no target=0.0.0.0/0 max-limit=100M/100M time=0s-10h,sun,mon,tue,thu,wed,fri,sat
add name=teste-time3 disabled=no target=0.0.0.0/0 max-limit=100M/100M time=0s-13h,sun,mon,tue,thu,wed,fri,sat
add name=teste-time4 disabled=no target=0.0.0.0/0 max-limit=100M/100M time=0s-14h,sun,mon,tue,thu,wed,fri,sat
add name=teste-time5 disabled=no target=0.0.0.0/0 max-limit=100M/100M time=0s-20h,sun,mon,tue,thu,wed,fri,sat

The queues teste-time 1 to 3 show as invalid, the 4 and 5 works fine.

Attached some screenshots.
Queue OK.png
Queue Invalid.png

2

I have similar problem..

i have queue with time: 19:00:00 to 23:00:00

It worked well on 5.25, but on 6.1 it’s red on list and doesnt work.
I can set “from” time in 00:00:00 to 15:59:59, but with 16+ its invalid

3

In my case the time set as the end time becomes invalid IF it is less than the actual time… so if the routers clock says it 8:46 pm you can’t have a rule set to 8:45 but it’s OK if it’s 8:47. BUT it will becoame invalid 2 minutes later, nice bug ehh? :smiley:

4

Make sure you have correct time on router, and that time is in the range.

Here is my setup,

 system clock 
[admin@S] /system clock> print 
            time: 18:06:20
            date: jul/02/2013
  time-zone-name: manual
      gmt-offset: +03:00
[admin@S] /system clock> /   
[admin@S] > queue export 
# jul/02/2013 18:06:23 by RouterOS 6.2rc1
#
/queue simple
add name=queue1 target=1.2.3.4/32
add name=queue2 target=192.168.100.0/24 time=\
    0s-19h,sun,mon,tue,wed,thu,fri,sat

See attached file.
queue_time.png

5

Yes, sorry for that, it´s a feature not a bug. Now, in ROS 6.x, rules will show up as invalid if they are outside the time range. It makes sense since before you couldn’t tell if a rule was “active” or not. :smiley: