queue 2.8 vs 2.9

RouterOS General
1

Hello,

Does anyone knows how this should be converted into ver 2.9.6:

ip firewall mangle add src-address=192.168.2.0/24 mark-flow=p2p-out p2p=all-p2p action=accept

ip firewall mangle add dst-address=192.168.2.0/24 mark-flow=p2p-in p2p=all-p2p action=accept

queue type add name=p2p-in kind=pcq pcq-rate=56000 pcq-classifier=src-address

queue type add name=p2p-out kind=pcq pcq-rate=56000 pcq-classifier=dst-address

queue tree add name=p2p-in parent=global-in flow=p2p-in queue=p2p-in priority=8

queue tree add name=p2p-out parent=global-out flow=p2p-out queue=p2p-out priority=8

ip firewall mangle add action=accept mark-flow=all

queue type add name=PCQ-Down kind=pcq pcq-rate=131072 pcq-classifier=dst-address

queue type add name=PCQ-Up kind=pcq pcq-rate=131072 pcq-classifier=src-address

queue tree add parent=global-in queue=PCQ-Down flow=all priority=1

queue tree add parent=global-out queue=PCQ-Up flow=all priority=1


best regards,

faton

2

This is the convertion in 2.9.6

Difference is no src-address and dst-address in mangle, and parents are interfaces, tested OK:

ip firewall mangle add chain=forward p2p=all-p2p action=mark-connection new-connection-mark=p2p_conn passthrough=yes

ip firewall mangle add chain=forward connection-mark=p2p_conn action=mark-packet new-packet-mark=p2p passthrough=yes

ip firewall mangle add chain=forward connection-mark=!p2p_conn action=mark-packet new-packet-mark=other passthrough=yes


queue type add name=p2p-Down kind=pcq pcq-rate=56000 pcq-limit=50 pcq-classifier=dst-address pcq-total-limit=2000

queue type add name=p2p-Up kind=pcq pcq-rate=56000 pcq-limit=50 pcq-classifier=src-address pcq-total-limit=2000

queue type add name=Down kind=pcq pcq-rate=128000 pcq-limit=50 pcq-classifier=dst-address pcq-total-limit=2000

queue type add name=Up kind=pcq pcq-rate=128000 pcq-limit=50 pcq-classifier=src-address pcq-total-limit=2000


queue tree add name=p2p-up parent=WAN packet-mark=p2p limit-at=0 queue=p2p-Up priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

queue tree add name=p2p-Down parent=LAN packet-mark=p2p limit-at=0 queue=p2p-Down priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

queue tree add name=Upload parent=WAN packet-mark=other limit-at=0 queue=Up priority=1 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

queue tree add name=Download parent=LAN packet-mark=other limit-at=0 queue=Down priority=1 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s


Regards,

Faton

3

On the 2.9 example above I get an error on the line adding the queue tree. I assume this has to do with parent=WAN. Something goes in the place of WAN? I assume this would be one of the interfaces. For instance on a wireless ap connection, the wlan1 would be LAN and the ether1 would be LAN?

tk

4

Hi,

WAN means the interface facing the public network and LAN interface facing the local network (clients), for example WAN can be an ether1 interface which connects to DSL modem, and LAN interface can be a 2.4GHz interface which connects clients.

p.s. I have named my interfaces WAN (public) and LAN (local).

Regards.

5

Had them backwards. Thanks for the help.

tk

6

Couple more questions on this.
In the 2.8 version of this it uses a parent of global-in or global-out. In the 2.9 version of this it uses the specific interface. Why the difference?

This next one looks like it has been discussed elsewhere several times but I don’t see a clear answer. It appears these rules are not catching UDP p2p. I know UDP is connectionless so is there another way?

tk