Community discussions

MikroTik App
 
UsRb
newbie
Topic Author
Posts: 46
Joined: Mon Sep 18, 2006 4:32 pm
Location: Europe - Croatia - Zabok
Contact:

Mangling WoW port 3724

Fri Aug 10, 2007 9:53 pm

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
 
UsRb
newbie
Topic Author
Posts: 46
Joined: Mon Sep 18, 2006 4:32 pm
Location: Europe - Croatia - Zabok
Contact:

Re: Mangling WoW port 3724

Sat Aug 11, 2007 1:17 pm

Anyone, some suggestions? It's really odd problem...
 
cpelect
Frequent Visitor
Frequent Visitor
Posts: 50
Joined: Wed Aug 30, 2006 12:17 am

Re: Mangling WoW port 3724

Mon Aug 20, 2007 10:04 pm

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
 
UsRb
newbie
Topic Author
Posts: 46
Joined: Mon Sep 18, 2006 4:32 pm
Location: Europe - Croatia - Zabok
Contact:

Re: Mangling WoW port 3724

Fri Aug 24, 2007 12:57 pm

Thx 4 your answer, but what is your mangle rule for packet-mark=wow?
 
User avatar
janisk
MikroTik Support
MikroTik Support
Posts: 6263
Joined: Tue Feb 14, 2006 9:46 am
Location: Riga, Latvia

Re: Mangling WoW port 3724

Fri Aug 24, 2007 2:35 pm

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
 
UsRb
newbie
Topic Author
Posts: 46
Joined: Mon Sep 18, 2006 4:32 pm
Location: Europe - Croatia - Zabok
Contact:

Re: Mangling WoW port 3724

Fri Aug 24, 2007 7:10 pm

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...
 
Lollo
newbie
Posts: 35
Joined: Tue Aug 07, 2007 9:10 pm

Re: Mangling WoW port 3724

Sat Aug 25, 2007 2:45 pm

I've got your very same problem :|
 
UsRb
newbie
Topic Author
Posts: 46
Joined: Mon Sep 18, 2006 4:32 pm
Location: Europe - Croatia - Zabok
Contact:

Re: Mangling WoW port 3724

Sun Aug 26, 2007 11:01 pm

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