Time Format

Why when i put time limit at my simple Qs the rules dont work?
For example: start time=17:30:00(5 and 30 afternoon)/End time=00:00:00 (midnight)
Is my understanding of this format correct or not?and if it is correct why the rules dont work when i put that time in its place?
Thanks in advance.
zaherhamiyah@hotmail.com

Have you set the time correcty on the MT? if youre using RBXXX, you must set a NTP client…

Regards

Dear i think this has nothing to do with NTP Client Or Server.
I am talking about the Time we set in Simple Queue to make it Working during that time from start to end.But the problem is that it didn’t work as mentioned above.

The rules might not work because the router has the wrong time?

[xxxx@DeltaNet] system ntp server> print
enabled: no
broadcast: no
multicast: no
manycast: no

[xxxx@DeltaNet] system ntp client> print
enabled: no
mode: unicast
primary-ntp: 0.0.0.0
secondary-ntp: 0.0.0.0
status: stopped

these are the conf of my NTP
but again i think this has nothing to do with NTP

If you know that the clock time is not the problem, why are you asking here?

Ohhhhhh God !!!
can u plz read the first post and then try to help me ?plz

name=“zaher” target-addresses=192.168.0.4/32 dst-address=0.0.0.0/0 interface=all parent=none direction=both
priority=8 queue=default-small/default-small limit-at=0/0 max-limit=24000/80000 total-queue=default-small
time=17h-1h30m,sun,mon,tue,wed,thu,fri,sat

This is a sample conf of my simple Q.
My question was about the time format time=17h-1h30m
i see 00:00:00(start time) and 00:00:00 (end time).
My request is some body explain this issue.
Coz i thought that 00:00:00 means HH:MM:SS and by applying this rule i found that i was wrong.
Thanks

The clock time is 24hs format, BUT if you have a wrong time in you’re clock it will not WORK…

How about if you tried to read the manual or maybe just tried to look at the console and read what it says?.. ok, the manual is less then readable on this subject but winbox gives a hint when the second field is “1d 00:00:00”

The time field for simple queues is starttime-duration,weekdays to use!

A time field 17:30:00-00:00:00 tells the router to start this queue at 17:30:00 and use it for exactly 0 seconds! :slight_smile:

/Jörgen

How about if you tried to read the manual or maybe just tried to look at the console and read what it says?.. ok, the manual is less then readable on this subject but winbox gives a hint when the second field is “1d 00:00:00”

The time field for simple queues is starttime-duration,weekdays to use!

Yes that what i thought , and thanks for your nice try.But the problem according to your explanation is not solved,why is that coz i tried it before and the answer is negative.And again why?coz when i apply the rule the counters dont work and when i disable it the counters work again.This is an example:
2 name=“customer’s name” target-addresses=192.168.0.11/32 dst-address=0.0.0.0/0 interface=all parent=none direction=both
priority=8 queue=default-small/default-small limit-at=0/0 max-limit=24000/80000 total-queue=default-small
time=17h-10h,sun,mon,tue,wed,thu,fri,sat

And this from the console help:
queue simple> add time=
At which time and day of week to allow this queue

Time ::= Start-End,Day
Start – time interval
End – time interval
Day ::= sun|mon|tue|wed|thu|fri|sat[,Day
]
*
The help inside console says start-End not start-duration
and if u look at time=17h-10h the logic says that the rule must operate from 5 PM till 10 AM in the next morning.And my local and server’s time is 00:20 AM so it must work but in reality it dont work???
Any clue about this?
i hope i explained the problem well.
NO BODY is PERFECT

Opps, my bad!

This is strange, now I have never used simple queues, I just looked at it to see if I could give you some help

Winbox in my case gives a strong hint that it should be start-duration (since it default shows 1d 00:00:00 in the end field), however when I try that it doesn’t work…

When I instead used the starttime-endtime it works for me..

add name="queue1" target-addresses=192.168.2.30/32 dst-address=0.0.0.0/0 \
    interface=all parent=none direction=both priority=8 queue=default/default \
    limit-at=0/0 max-limit=0/64000 total-queue=default \
    time=9h-9h40m,sun,mon,tue,wed,thu,fri,sat disabled=no

This queue made it hard for me to surf… as it should since I only get 64K :slight_smile:

However… I can’t seem to see the amount of traffic in the SSH-terminal, it’s only visible in winbox. Or I might not have found the proper comands yet.

Are you sure your problem lies with the time format and not with some other setting? If you create a most basic simple queue in winbox (just the target IP and the time field) do you see the counters change?

/Jörgen

/Jörgen

Are you sure your problem lies with the time format and not with some other setting? If you create a most basic simple queue in winbox (just the target IP and the time field) do you see the counters change?

And that’s my friend why they call it Simple Queue to make our lives more complicated :laughing:
This problem is so Weird.
:open_mouth:

I think what someone else was trying to get at is that are you sure your local clock (/sys clock) has the right time?

I really can’t help much, but one question relating to this…how does the queue (or the router for that matter) know what day of the week it is? I’m not seeing anywhere in the router a day that associates to the current date? I wonder if this is a hidden setting that only works if your ntp client is configured and running?

it is a known problem that if you adjust DTS settings for the clock, then rules do not see these changes. either set rules with this in mind, or don’t use DST