With “Use IP Firewall” enabled, I often run a simple queue on a port. Periodically, that queue will only limit upload, not download.
I just moved a port that was running correctly (with a queue applied to that port) from one bridge to another. Now that queue only works on upload, not download.
I created a new queue with the same parameters, but it still does not work correctly.
Is there a specific order in which to add a port to a bridge and then add a queue?
Not sure how the rest of your config works… Here’s an example that I threw together where I can limit the download and upload of a specific IP behind my Mikrotik using simple queues.
Flags: X - disabled, I - invalid, D - dynamic
0 XI name="Test" target=10.10.25.66/32 parent=none packet-marks="" priority=8/8 queue=default-small/default-small
limit-at=0/0 max-limit=512k/512k burst-limit=768k/768k burst-threshold=768k/768k burst-time=10s/10s
I’m limiting the speed on a port-by-port basis. I’ve generally had trouble with port speed queues, but I thought I had the issue resolved. It has been working correctly for months. All I changed was the bridge the port was connected to.
The only connection to this port is through a bridge. I changed the bridge port, and now the download is unlimited on the queue, even though the queue has not changed.
I’ve tried re-entering the queue, but it does not help.
If I check in WinBox, the queue now shows two targets. BUT, in the CLI, printing the queues and the configuration export only shows ether2. Is there something I’m missing here?