I am trying to make a queue to limit all p2p on subnet 10.20.1.0/24 to 1kB/s from 20:00 to 01:00 hours.
The limit works, but all the time, not only between 20-01.
Is it a bug with 2.9.2 version or it should be done somehow different?
This will be fixed in the next release.
I also have this problem, and i posted it on the forum http://forum.mikrotik.com/viewtopic.php?t=4373&start=0&postdays=0&postorder=asc&highlight=simple+queues+feature. But I’m now so glad to hear that this problem is going to be fixed in the next release. Thanks so much Eugene!
Anyone tried that time limit in 2.9.7 version?
It still doesn`t work for me. I have set it 20:00:00 - 23:00:00, but the traffic is limited to 1kB/s all the time, not only at preset time.
how about latest version 2.9.11 ??
I haven`t tried 2.9.11.
Here is changelog for 2.9.7:
What’s new in 2.9.7:
*) fixed bug - web server could crash sometimes (introduced in 2.9.6);
*) fixed traceroute time display;
*) added route rule configuration;
*) fixed performance problem with universal client on RB500;
*) improved dynamic wireless rate selection;
*) updated WPA to work with Netgear WGE111;
*) added hotspot ip-binding changes to take effect immediately;
*) fixed M3P;
*) fixed queue time limits;
*) added direction matcher to simple qeueues;
*) fixed problems with graphs;
It works fine for me starting 2.9.7 - but I’m using 2.9.10 now. Perhaps, you have another set of firewall rule that is located before this one?
Another thing: It seems the time limiting feature cannot work for the entire time period if you set it for a time period that goes over midnight (e.g. 20:00:00 - 08:00:00). In this I case I have to split it into two different rules (one that goes 20:00:00-24:00:00 and a second one for 00:00:00-08:00:00). Any one has idea how to do it with only one firewall rule? The new MT version seems to have an additional date field (1d 00:00:00), and I need to find out how to take advantage of it I guess.
No, I have only one simple queue rule which has that time limit included and it doesn`t work as it should. I tried many time limits (16-17, 20-23..) and none of the them work.
I am really stuck…
If someone is interested, I have found a workaround for this.
Since time limit in simple queue did not work, I used time limit in mangle in packet-mark and now everything work, even in 2.9.6 version.
That’s the way we do it - time limits in mangle for different rule sets, then queue the different packet marks which only get marked at certain times…
Only thing that doesn’t seem to work is we use an NTP server to synch all the times, but the mangle time rules don’t seem to synch with that. We have to adjust the time according to the GMT difference on each rule…