Mangling WoW port 3724

RouterOS General
1

Hi2all,

I have set up port forward for WoW and it works fine. But I want to make good traffic control for it. Now, I have queue trees set up for 3 more games and it works fine. The problem is I can’t join WoW unless I disable mangle rule. Then I join and for low latency I must enable it back again. Plz, does anyone has same experience and knows how to solve it so I don’t need to disable the mangle every time? Here is my configuration:

Mangle:
chain=forward src-address=10.19.0.0/16 dst-address=!10.19.0.0/16 protocol=tcp dst-port=3724 action=mark-packet new-packet-mark=upload_high passthrough=no

Queue:
name=“Igre” parent=Upload packet-mark=upload_high limit-at=100000 queue=PCQ_upload priority=1 max-limit=130000 burst-limit=0 burst-threshold=0 burst-time=0s

Port forward:
chain=dstnat src-address=!10.19.0.0/16 protocol=tcp dst-port=3724 action=dst-nat to-addresses=10.19.0.0-10.19.255.255 to-ports=3724

10.19.0.0/16 - local network

2

Anyone, some suggestions? It’s really odd problem…

3

I was able to build a queue for WoW using these rules.

Mangle:

;;; WoW Packet Mark
chain=forward connection-mark=user-wow action=mark-packet new-packet-mark=wow passthrough=no 

chain=forward protocol=tcp src-port=1024-65535 dst-port=3724 action=mark-connection new-connection-mark=user-wow passthrough=no

Download Queue:

name="d2" parent=Download packet-mark=wow limit-at=64000 queue=pcq-download priority=2 max-limit=3072000 burst-limit=0 burst-threshold=0 burst-time=0s

Upload Queue:

name="u2" parent=Upload packet-mark=wow limit-at=32000 queue=pcq-upload priority=2 max-limit=1024000 burst-limit=0 burst-threshold=0 burst-time=0s

I hope this helps you in some way.

~Sean

4

Thx 4 your answer, but what is your mangle rule for packet-mark=wow?

5

as cpelect wrote:
Mangle:

;;; WoW Packet Mark
chain=forward connection-mark=user-wow action=mark-packet new-packet-mark=wow passthrough=no

chain=forward protocol=tcp src-port=1024-65535 dst-port=3724 action=mark-connection new-connection-mark=user-wow passthrough=no

this is how he is marking connection and then using this connection mark marks packets

6

When I set up this configuration, packets are passing only through connection mark, and not through queues, so latency is terrible… But, 1 problem is solved, I don’t have to turn manually on and off mangling every time. Still, latency is to be solved…

7

I’ve got your very same problem :neutral_face:

8

I put connection mark with passthrough=yes. I need to test it for few days to see latency behaviour.