Hello
Is there å good way to rate limit layer 2 bridges (WDS)?
I tried the simple Queues, but it does not seem to have any affect.
I want both rx and tx rate limit.
Hope somebody has tips
/interface bridge settings set use-ip-firewall=yes
WOW, Out of all the simple queue threads I read, this one worked! THANK YOU.
As a realitivley Newbie, I don’t understand why the Use Ip firewall works for the simple queue, but I see that it works.
Because otherwise bridged traffic does not pass through the routers’ routing facilities prerouting, forward, and postrouting, where the global-* queues are, that the simple queues create rules in. For more info - see WiKi manual pages about IP Flow (Packet Flow), and about Queues and such. http://wiki.mikrotik.com/wiki/Packet_Flow
Ok I found a bug…
I connect this PC to a DVR’s video stream at our shop, it gets about 11 - 12 Mbit/s over the wireless… ( On a rb112 to a 532A)
I create a simple Queue for 2 Mbit, up and down, on interface ther 1 ( which connects to our firewall/switch) the speed drops to 2 mbit. Good, works.. ( this was just for testing)
But when I change the speed to anything else, it stays at 2 Mbit.
I have tried to close the queue properties window, disable the queue and re-enable it, but ti still stays at 2. I looked under teh general tab and advanced tab to make sure they were both at the new setting, which was 3m bit, and even added 3mbit under the total, Nothing works.
The only thing that works is deleting the rule, and creating a new one.
The other thing I noticed when you originally create the rule, it counts traffic in Total Bytes Tx’d and Rx’d but when you change the limit higher or lower, it stays at the original speeds ( as described above) and does NOT count traffic.
Now I have seen alot of posts regarding the issue of simple ques not working, and this MIGHT be what people are reffereing to.
I Just tried it again, when the rule was created and had UNLIMITED set in it initially and apply was clicked, it was well, unlimited, then I could change the rule to 2 Mbit, and it switched to 2 Mbit speeds. when I changed the rule to 1 Mbit, I saw the speeds drop for about 2 seconds to 800K then went back to 2Mbit and stayed there.
As for not counting traffic, this rule does count traffic, excpet the total RX bytes, BUT I corrected this as my rule was set for ETHER1, and the RX bytes showed up when I put the interface to all. Assuming Bridge interface, and no other ether is connected. but bridge is not listed in the interface list, or even wireless card for that matter.. wierd..
running 3.20 on this one.
THERE IS something definatley wrong here as the updating of the queue is not working…
Ok WIerd again, I just tried changing the speed of the queue and it is chaging the speed. I have no clue…
This is even stupider… Ok, so Upload means DATA SENT, Download, Data recieved… right.. in lamens terms..
so, my rule applies to ether 1, Target download is set 2Mbit, and I recieve 2 mbit on the PC, BUT, Does it make more sense to have the target download, Meaning, the ETHER1 ( or which ever interface) you set it to, whouldnt this mean the amount of data the atcual PORT is recieving?
Like I set the target upload to 1Mbit, rule is for ether 1, I read that as Ether 1 should SEND data at 1 Mbit, but it stays at 2 ( Target download is now set at 2, but if Target down is set to 1 it goes to 1mbit speed.)
The test pc is connected via a firewall and ether 1 on this 532A.
I put in an IP address of this PC under the advaced tab, and it doesnt even limit the speeds. if I put in the IP of the DVR server in the DST addresses, it limits the rate to 2Mbit, *** BUT ** all my rates right now are set to 1 mbit, on general and advanced tabs, Nothing in the Total Tab.
Basically there is something messed up here…
My understanding of this, please correct me if I am wrong:
The Upload and DL limiting should be the relation between the PORT and the device specified in the IP address IF one is specified, and if not, it will apply to all connections, via that port. if Under the destination address I put the IP of my PC, I would assume that the term Target Upload means how fast that PC can send data to that port ( or is it how fast the port will “listen” 
)
Why cant we just make it simple and have that as Interface TX rate, and interface RX rate, that way it refers specifically to the PORT, and the dst address would apply under that, eg settings of Interface RX speed of 2Mbit with IP address of 10.10.10.50 will allow that IP to send data tot he port at 2 Mbit. and vice versa for the Interface TX speed.
RIght now I have the queue set to 10.10.10.135 which i the DVR IP address, On ether 1, and Download rate is what changes the speed to MY PC. If the rule is set to the dst address of the DVR, and that is considered the Target, and the Target DL rate is set to 2 Mbit, Why does my PC get the rate of 2 Mbit? I can see if I set it under Target upload to 2 Mbit, that it would limit to 2 mbit, but that does nothing. basically this is backwards.
But I jsut thought of something, If you set DL rate on ether 1, technically I guess the rate recieved by the ether would be considered a DL to the port. BUT, the data first goes through teh WLAN port. I would assume that a DL on ehter 1 is data that is comming IN on the physical port of ether 1, not across the bridge of wlan1 to ether 1.
Am I out to lunch on this? I could of sown before this did not work in this fashion.
ok, I’m done typing!
Ok I’m not…
Just went to go sleep, deleted my queue rule, but the data still stays at 2 Mbit.. WHy?, rebooted the 532A ( running 3.20) and came back on. tried to add new queue, well jsut to see if ther rest of the ports were there, and they were, where as before teh reboot they ended up dissapearing, there was only ether ports listed, 1,2 and 3. Now I have the ether, WLAN, Bridge, and WDS listed as ports.
This is definatley a bug.
do the not-working config and gerenate a supout.rif file (the menu in WinBox) , then grab it from “Files” and send it to support@mikrotik.com, paste them the link to this post/explain to them.
P.S. It seems that you are a bit confused. So please post the config of your simple queue and tell us with a short sentence what the problem is. You could help us help you even better if you post screenshots as well. Although I myself prefer to have WinBox access to see and click for myself.
I was told earlier in the week, that ROS 3.21 was tested for this issue that I described, and that it didn’t have the problem. I was also told that 3.21 would be released this week, but, it hasn’t been yet… 1 day to go though! you never know.
Makes me wonder though… THe response I got was that it didn’t do this in 3.21.. but the real question is, did you know about it in 3.20, or why didn’t they test it? I have no clue, maybe no time.