Community discussions

MikroTik App
 
BeNBeN
just joined
Topic Author
Posts: 18
Joined: Fri Oct 09, 2009 3:13 pm

Qos or setting piority for world of warcraft

Mon Oct 12, 2009 5:54 pm

My mikrotik works as pppoe server for clients and there are about 1200 clients connecting to internet on mikrotik. Sometimes internet connection can be really busy. On that times, my clients who play world of warcraft(wow) has packet loss or high ping. I want them to play with low ping and I research about wow and I found its using port 3724. I want to set piority to 3724 port and my question is how can I?? Thanks...
 
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1770
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: Qos or setting piority for world of warcraft

Wed Oct 14, 2009 4:17 pm

Find the address ranges owned by Blizzard Entertainment and prioritize all traffic comming and going to those addresses. Basic principles in post above.
 
BeNBeN
just joined
Topic Author
Posts: 18
Joined: Fri Oct 09, 2009 3:13 pm

Re: Qos or setting piority for world of warcraft

Thu Nov 19, 2009 9:48 am

I've found layer-7 regexp for wow. if I set piority 1 for that packets in firewall mangle, does it work? I am new at mikrotik and I know myself. I am a good learner with examples then explanations. Not starting with explanations. The language is also a problem for me because english is not my own language but it is not a huge problem also. Thank you guys.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8712
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: Qos or setting piority for world of warcraft

Thu Nov 19, 2009 4:54 pm

actually, this priority is simply inserted into VLAN tagged packets or WMM wireless packets. to prioritize packets inside the router, you need to use queues
 
jherrick
just joined
Posts: 20
Joined: Fri Aug 07, 2009 3:39 am

Re: Qos or setting piority for world of warcraft

Thu Nov 19, 2009 9:00 pm

Try the following, i use masquerade, so that is why im using global_out as my downstream parent. Im not 100% positive it is set up correctly.. and sorry for no comments. Maybe someone can spot check the queues and mangle rules and confirm that priority will work... packets flow through fine, so i assume it works... but packets flow'd before their was parent queue as well... I believe its set up right with the priority set on the leafs now.

/queue tree

add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=10M name=downstream_qos packet-mark="" parent=global-out \
priority=1 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=1M name=upstream_qos packet-mark="" parent=wan1 priority=1 \
queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=10M name=lan_qos_low packet-mark="" parent=downstream_qos \
priority=8 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=10M name=lan_qos_high packet-mark="" parent=downstream_qos \
priority=8 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=1M name=wan1_qos_high packet-mark="" parent=upstream_qos \
priority=8 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=700k name=wan1_qos_low packet-mark="" parent=upstream_qos \
priority=8 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=5M \
max-limit=10M name=lan_wow packet-mark=wow parent=lan_qos_high priority=1 \
queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=512k \
max-limit=1M name=wan1_wow packet-mark=wow parent=wan1_qos_high priority=\
1 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=5M \
max-limit=10M name=lan_vent packet-mark=vent parent=lan_qos_high \
priority=2 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=512k \
max-limit=1M name=wan1_vent packet-mark=vent parent=wan1_qos_high \
priority=2 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=350k \
max-limit=700k name=wan1_low_prior packet-mark=low_priority parent=\
wan1_qos_low priority=8 queue=default
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=5M \
max-limit=9M name=lan_low_priority packet-mark=low_priority parent=\
lan_qos_low priority=8 queue=default


/Ip firewall mangle

add action=mark-packet chain=postrouting comment="" disabled=no dst-port=3724 \
new-packet-mark=wow passthrough=no protocol=tcp src-address=\
192.168.1.0/24
add action=mark-packet chain=prerouting comment="" disabled=no in-interface=\
wan1 new-packet-mark=wow passthrough=no protocol=tcp src-port=3724
add action=mark-packet chain=prerouting comment="" disabled=no in-interface=\
wan1 new-packet-mark=vent passthrough=no protocol=tcp src-port=5421
add action=mark-packet chain=postrouting comment="" disabled=no dst-port=5421 \
new-packet-mark=vent passthrough=no protocol=tcp
add action=mark-packet chain=forward comment="" disabled=no new-packet-mark=\
low_priority passthrough=no

good luck!