I have set up a simple queue for my sip phone with ip address 192.168.15.250. Using winbox, double clicking on the “Sip phone” que and then on the Traffic tab, the graph shows neither Tx nor Rx traffic. However, when I click on the Torch button, I can see TX rates of 80kbits and RX of about 80 kbits.
Why is the “Traffic” graph not showing traffic but torch is?
In the simple queue, try setting “queue type” to “default” vice “default-small” and try setting interface to “All”. Also make sure there is not another queue limiting the ip address or a range of addresses.
Thank you. I tried this and it still did not work.
I then created a new simple queue that did graph traffic. When I copy this new working queue in winbox, the new queue will not graph traffic. Is this possibly a bug in winbox?
I too cant comprehend why this wont work…
I really need like a true lamen explination as to why please.
I just bought a 493 AH, bridged ports 2 - 6. Port 2 is the WAN ( cable connection) and ether 3 is the one to the basement, which is the one I want a simple throttling on. Ie I want to limit thier Upload since they use alot of file sharing for music etc.
so I setup a simple queue for Ether 3 limit at 128K up and down, doesnt work, I read forumn, and read some more, I try the interface bridge set use ip-firewall=yes and this does not work. I look at the traffic in the simpel queue it shows a minor amount of data, about the same that is going over the bridge interface, BUT the upload rate on ether 3 is like 500K/sec while the bridge data is like 20kb/s. The simple queue only shows Download, and 0 for upload.
This all happens when I set the port on the simple queue to ether 3, so why is the data representitive of the data on the bridge? Why after specifying the ether 3, it doesnt work?
I tried to go to the Interfaces, ethernet tab in winbox, and then set tx/rx rates, it only allows 1mbit, 2, 4 and 8.
I read alot of posts about this. and I cannot understand why it is not working, simple queue on that ether port should work, but it does not. I do recal VERY clearly that in 2.9.51 it worked with this described setup, and Yes, I know there was a change in how queue rules were handled, just dont know how, other then they do not work.
If you have created a bridge interface ‘bridge1’ with ports of say, wlan1 and ether3, then you must put the queue on interface ‘bridge1’ not the ether3 interface. You cannot apply rules to the individual ports, such as wlan1 or ether3, only to the bridge interface.
Ron
So I was wasting my time trying 
Perfect…
Ok, so what you are saying in my set up, I cannot do this simple thing:
Have ether 1 as WAN ( Cable connection )
Ether 2 as VOip Phone ( in bridge with ehter 1 and 3 to allow for public IP to voip device I get 5 public ip’s)
Ether 3 as basement connection for tenants ( this is the port I want to throtlle.
So if those 3 are in a bridge, i cannot set a queue rule just on ether 3, but I can on the bridge. How would one go about controlling data to just that one ether port, if the queue was placed on the bridge? I cant recall if I tried, BUT, if I put a queue on the bridge, to use with destination and/or source address being what is assigned to the basement router ( Public IP) then in theory I should be able to control this? But the funny thing is, that very little traffic goes across the bridge, when the DL rate is 10 mbit, it shows about 50k download on the bridge, but ether 1 Incomming is 10mbit,a nd ether 3 out is 10 mbit. So HOW do you control ANYthing witha queue if it can ONLY be set on the bridge, and the traffic does not actually flow on the bridge.
But the best question is, why did 2.9.51 allow you to control a physical ehter port when it was in a bridge?
I have also tried to put ether 2 and 3 as slave to ether 1 to create a switch with those three ports, but can’t see any data in winbox on those ports.
I would like to allow ether 2 and 3 to obtain an IP across the bridge from the WAN on ether 1, that would be nice, this way I could use ether over IP tunnel to other Rb’s to have direct access to a public IP.
Is there ANY way to do what I am trying to do, in simple form, control ether 3 speeds without touching ether 1 or 2. If ether 1 - 3 are in bridge, or not in bridge. The ether 3 connects to the tenants router/wlan, and is supposed to get a public IP from my isp, that Is why I put those ports in a bridge, and the VOIP on ether 2 doesnt need a public IP, but is better since I have a few VOIp’s behind the Natted part of the network. I get 5 public Ip’s, dynamic, from my isp.
if this cant do this, then I just spent alot of money on a rb 493ah that cant do what I thought was a simple thing for this board to do.
You have not wasted TOO much time, or money! Honest. I suggest you read the wiki article below first, it might help you realise why bridging and queues are not working. Once you read the wiki you will realise why.
http://wiki.mikrotik.com/wiki/Packet_Flow
Ron
\
[spoiler alert]
.
.
.
.
.
/interface bridge settings set use-ip-firewall=yes
I have found the bug, that was making me go crazy, where it wasnt behaving as expected, so that is why my issues were there, the bug was reported, confirmed and will be fixed. I did have another thread about it, but the issue was this ( Briefley )
using winbox, creating a queue rule, and setting the target Download to 1Mbit, on the general and advanced tab will limit the rate, and does change the speeds when you change the rate on BOTH the general and advanced tab. Where my issue was coming up was when you change the rate under advanced tab higher then what it is on the general tab, you get an error like Limit in higher then Max limit in, you click ok, then change the rate on advanced and general tab to the higher rate, I cant recall if it changes at this point, but after you try to change it to another rate, the rate stays the same as it were before you get the error message, either higher or lower will no change the rate.
Upon reboot the queue rule works at the rate set. But if you delete the queue rule, the bridge interface(s) dissapear from the list of interfaces. Rebooting will show the bridge interfaces. This problem is apparetly related to the queue rate limit issue as well.
As for setting the Interface in the queue, I was told several times that if the ether port is in bridge, then I have to use the bridge as the interface, no the ether port, other wise it would not work. I found different, setting my interface in the queue to ether 6 worked, and the rate worked properly.
My, and I am sure many others accidently set the rate higher under advanced then under genral and then the queue rule did not work properly, thus, creating confusion as to queue rules working or not, I know it confused me, but after HOURS and HOURS I tracked that glitch down and it will be addressed. Now knowing this is a bug, I can create rules ( ha I only actually needed one rule too!!!) and worka round the bug.
But I did understand all them block diagrams after I fooled around with changing the rates and especially the interface in the queue. Suddenly the block diagrams and arrows started to make more sense! Almost a professional now…