PCQ Queues work only when packet sniffer is running (bug?)

RouterOS General
1

Hello all!

I have the next config. Keep in mind that VLAN20 is the WAN and ISP is the bridge where my service VLANS live:

/ip firewall mangle
  chain=prerouting action=mark-connection new-connection-mark=conn-30.30 passthrough=yes src-address=172.16.71.0/24
  chain=prerouting action=mark-packet new-packet-mark=pack-30.30 passthrough=no connection-mark=conn-30.30
 
 /queue type
  name="DL_30M" kind=pcq pcq-rate=30M pcq-limit=50KiB pcq-classifier=dst-address pcq-total-limit=2000KiB pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=10s pcq-src-address-mask=32 pcq-dst-address-mask=32 pcq-src-address6-mask=128 pcq-dst-address6-mask=128 
  name="UL_30M" kind=pcq pcq-rate=30M pcq-limit=50KiB pcq-classifier=src-address pcq-total-limit=2000KiB pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=10s pcq-src-address-mask=32 pcq-dst-address-mask=32 pcq-src-address6-mask=128 pcq-dst-address6-mask=128

/queue tree
  name="BAJADA_PITERAS" parent=ISP packet-mark="" limit-at=0 queue=default-small priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1 
  name="SUBIDA_PITERAS" parent=VLAN 20 packet-mark="" limit-at=0 queue=default-small priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1
  name="BAJADA_30M" parent=BAJADA_PITERAS packet-mark=pack-30.30 limit-at=0 queue=DL_30M priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1 
  name="SUBIDA_30M" parent=SUBIDA_PITERAS packet-mark=pack-30.30 limit-at=0 queue=UL_30M priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s bucket-size=0.1

I’ve done this config a lot of times in previous versions of RoS 6. Now I’m using 7.10.2 and the limit works only in upload. Download is not limited. Am I doing something wrong?

Thanks in advance.

2

Okay guys. I found something interesting. Maybe this is a bug?

I’ve been making a lot of tests to find out what is the problem so I can solve it.
I found that, when I’m downloading, Mangle rule Statistics only show a few kbps (even when downloading @ 50Mbps). So I thought: maybe I did something wrong in the mangle, but checked and checked again and everything is fine.
So I say: let sniff packets to see if maybe RoS7 handles this in other way.
I turn on packet sniffing, and inmediately, mangle statistics start to show the real traffic and queues start to work. I disable packet sniffing, statistics go back to few Kbps and queues stop limiting.
Here a few pics (while downloading from the client):

  1. Packet sniffer stopped:




2. Packet sniffer running:





Let me know if I’m loosing something.

Thanks in advance!

3

Without a complete config, it seems that you are only limiting traffic marked from LAN (with src address) going out to WAN in the prerouting chain. Please check pcunite’s thread for the correct way to mark all traffic so downloads are also limited. You can also con mark by interface - it’s less efficient because you have marks for in and marks for out, but it works

4

And why does it work perfectly when I enable packet sniffing? This is the way I’ve been using for years in ROs 6.4 and never had a problem.
Also, I tried the same config in CHR (same version), and it works without the need to start packet sniffing. Again: a bug? (I’ve tested in two hEX’s, version 7.12.1 and got same problem). Tomorrow I’ll test with RB110AHx4 and RB2011

Anyway, I’ll give a try to the method you said.

5

I’m really, really, really sorry.

I was sure I disabled fasttracks connections, but it seems in some point I reenabled it and forgot about it.

Disabled fasttrack and everything is working as it should.

Again, I’m sorry. :cry:

6

No problem, happy you got it working…