The above rules are the ONLY mangle and queue tree entries in my device.
In this situation, should winbox under Queue List/Queue Tree show a non-zero packet count for the “special” queue after 117.53.171.171 is pinged or its web site accessed?
It doesn’t. I’m quite confused as to why not. I don’t believe that the packet marking is working.
All I am trying to do here is to successfully mark all incoming and outgoing packets to 117.53.171.171, and I would have thought that the packet counts would appear in the queue tree visible in winbox.
My ultimate goal is to prioritise VOIP[SIP/RTP] traffic via dscp info from TCP packets on the network, and I have followed various documents on the internet to try to accomplish this, but it doesn’t work for me, and I narrowed it down to this tiny example, which doesn’t work for me either.
I figure that if I can get this tiny example working then I can get the SIP/RTP issue solved too.
At this point, it seems to me like mangle is completely broken but there must be something I’m doing that is the cause…but I just can’t find it.
1.) A queue tree on WLAN1 will only affect the download side of the traffic for starters (assuming that is your LAN side of the router). You’ll need another queue tree on the WAN interface to get upload traffic as well.
2.) You don’t have a max-limit set on your “special” queue, without that the queue has no idea what it is capable of, so it does nothing.
3.) Your queue’s max-limit should be roughly 90% of what is capable of any given link, so if your download is 10Mbps, the queue tree should have a max-limit of 9Mbps.
4.) You are marking in the wrong chain for your mangle rules, with your current queue trees, forward works best as it is after dst-nat and before src-nat, so the router can tell where the packet is headed and where it came from.
The scenario here is I have a wireless link between two sites. The wlan interface on the client side is the WAN, and the ethernet interface on the access point side is the WAN.
So should I put a queue tree on WLAN1 on the client side to control uploads, and a queue tree on WLAN1 on the access point side to control downloads?
That would mean that the wiki page at http://wiki.mikrotik.com/wiki/DSCP_based_QoS_with_HTB is at least partly wrong. It does the same thing. I got the initial rule patterns from there. But the people there said it works (???).
Anyway I’ll set that.
I have had absolutely no success with getting any mangle rules visibly working at all, even on the forward chain, and I’m starting to believe that mangle is completely non functional at least with this firmware. RouterOS 5.5, firmware 2.29.
Consider the following as a simple test to see if mangle works, as the only mangle rule. I would have thought that it would set the dscp for UDP packets, but using the packet sniffer in detail mode, even on the other end of the link shows me that the DSCP (TOS) values have not changed. I have tried this rule on prerouting, postrouting, output, and forward, and it doesn’t seem to do anything.
My suspicions were correct… there were NO PACKETS whatsoever appearing in the forward chain even though the device was working forwarding packets.
The reason was that I’m using the device in bridge mode, and if you in winbox go into the bridge and click settings, “Use IP Firewall” needs to be checked for the packets to appear in the forward chain!!! Once that is checked, then you get packets in the forward chain.
