I think I found a bug in CRS125 running ROS 6.5, and it’s still there after upgrading to ROS 6.7
I want a bandwidth to/from all destinations except for one particular subnet to be limited
(All local subnets on this box is within 172.27.0.0/16 the range)
According to how I read documentation the following commands would make communication to/from the 213.236.250.0/26 subnet unlimited, while anything else would be limited to 512k.
/queue simple
add dst=213.236.250.0/26 name=queue-office target=172.27.0.0/16
add max-limit=512k/512k name=queue-public target=172.27.0.0/16
However, the 512k limitation seems to apply even to the 213.236.250.0/26 subnet. Monitoring traffic in winbox I see that all packets hits the second rule, no matter where they come from. (Swapping the order of the queues did not make any changes.)
Now, if I delete the queues created above, and rather run these commands:
/queue simple
add max-limit=20M/20M dst=213.236.250.0/26 name=queue-office target=172.27.0.0/16
add max-limit=512k/512k name=queue-pub target=172.27.0.0/16
… the packets to/from 213.236.250.0/26 hits the first rule, and they are not limited by the 512k limitation.
So it seems to me that when a simple queue is created using “unlimited” the queue is ignored.
Workaround: set limit so higher than link speed.
Googleing turned me to this video, which also show that when queue is set unlimited, the queue doesn’t hit. http://www.youtube.com/watch?v=VImqaJEbAAk