UDP/TCP port number for QoS
#1
Posted 31 October 2012 - 11:01 AM
Been googleling to try and find what port numbers are being used by the game. Not found anything so far. Would like to add it to the QoS on my router. Lagging a little with Windows background coms.
Any help would be much appreciated.
Regards
Lian
#2
Posted 31 October 2012 - 11:07 AM
Quote
Hello Stickjock,
Second, make sure to open the following ports:
TCP 45461
TCP 45464
UDP 21000 to 30000
If it still doesn't work, please let me know and we'll dig deeper.
Regards,
Justin Xyang
GameMaster
MechWarrior® Online™
A little old, but these where the ports I was told to open up when I had some disconnect issues back in August... imagine they're still the same but you could always email support@mwomercs.com to make sure...
#3
Posted 31 October 2012 - 11:08 AM
Last time I checked, all game traffic was coming from 70.42.29.74.
EDIT: "UDP 21000 to 30000" - Yeah, I would not create a QoS rule to watch 9000 ports. You will almost certainly end up mis-categorizing traffic.
Edited by knnniggett, 31 October 2012 - 11:12 AM.
#4
Posted 01 November 2012 - 12:30 PM
Had a look at Resource Monitor and 45461 was there so just extended the range to 45464 on my router. I believe that is it. Have been getting a more stable latency since then.
Thanks again
Lian
#5
Posted 04 November 2012 - 12:50 PM
knnniggett, on 31 October 2012 - 11:08 AM, said:
Last time I checked, all game traffic was coming from 70.42.29.74.
EDIT: "UDP 21000 to 30000" - Yeah, I would not create a QoS rule to watch 9000 ports. You will almost certainly end up mis-categorizing traffic.
Lil confused... did u do this in your windows firewall or the router itself?
the only qos settings my router offers me are tcp/udp and mac addresses... nothing for ip's less u used port forwarding or so..
do explain ! plz!
#6
Posted 04 November 2012 - 01:29 PM
Crazycajun, on 04 November 2012 - 12:50 PM, said:
Lil confused... did u do this in your windows firewall or the router itself?
the only qos settings my router offers me are tcp/udp and mac addresses... nothing for ip's less u used port forwarding or so..
do explain ! plz!
This is done at the router and capabilities vary by router. Honestly unless you're internet connection is getting maxed out on the upload or download QoS won't net you any gains or benefits.
#7
Posted 04 November 2012 - 01:45 PM
Aurien Titus, on 04 November 2012 - 01:29 PM, said:
This is done at the router and capabilities vary by router. Honestly unless you're internet connection is getting maxed out on the upload or download QoS won't net you any gains or benefits.
Have to say, didn't seem like the changes they had me make made any difference... would drop randomly after battles/etc... again, this was back in August tho'... and since then have had no problems with my connection here...
Just gave him the infor support had given me back then...
Best bet tho' would be to email support@mwomercs.com and check with them...
#8
Posted 04 November 2012 - 02:41 PM
If something else on your home network develops issues while you play the game, then you might benefit from QoS.
If you are trying to implement QoS because the game itself is having issues then I would recommend you first try the following:
Set your equipment & software up so that you are certain nothing else is using the Internet. Plug your gaming pc directly into your cable/dsl modem if you can. Play the game, and if the issue(s) are still there then QoS will not help in this situation.
If the issues do go away then QoS might help, but it is still hard to say. More data is still needed.
Another downside is that most home routers have very limited QoS features, and they typically provide no feedback to tell you it is working right.
If you really want to roll up your sleeves and try this out, then for starters we will need the make & model of your router.
#9
Posted 23 November 2012 - 12:24 AM
Lianesch, on 01 November 2012 - 12:30 PM, said:
Had a look at Resource Monitor and 45461 was there so just extended the range to 45464 on my router. I believe that is it. Have been getting a more stable latency since then.
Thanks again
Lian
like tcp ports 45461 to 45464 for gaming.. just configured - works. but not sure about VIOP/TS ingame
Edited by no1337, 23 November 2012 - 12:25 AM.
#10
Posted 28 December 2012 - 10:28 AM
Protocol: IPv4 TCP
Destination: 70.42.29.0/24
Port: 45461 - 45464
Queue: qACK/qGames
and
Protocol: IPv4 UDP
Destination: 70.42.29.0/24
Port: 21000 - 30000
Queue: qGames
The ability to specify the destination address/network too makes it possible for me to have the large port range without unintended traffic going to the queue.
Edited by Monitus, 28 December 2012 - 10:29 AM.
#11
Posted 28 December 2012 - 10:47 AM
It's great how you can see each traffic shaper queue populate in real time.
I just upgraded to pfsense 2.0.2 last night. The upgrade was as smooth as expected.
#12
Posted 28 December 2012 - 11:02 AM
that might be easier than hunting down PGI IPs (which may or may not change in the future without you knowing it).
#13
Posted 28 December 2012 - 11:42 AM
Kaemon, on 28 December 2012 - 11:02 AM, said:
that might be easier than hunting down PGI IPs (which may or may not change in the future without you knowing it).
Well, I try not to use Windows, but these game developers just don't want to cooperate.
Yes, you're right regarding the Windows firewall, but the topic is about QOS, which is not the same thing as punching holes in a firewall to allow certain traffic to pass.
QOS allows one to prioritize the traffic that is already flowing through the firewall (i.e. you've already enabled the traffic to pass through the firewall via a rule but now you want to make it more important than certain kinds of other traffic). One does that so that the game is not affected, for example, if someone on another networked computer starts up a bittorrent session. ...A bittorrent session that downloads the latest copy of your favorite Linux distribution of course.
Lastly, this is something you need to set up on a networked device that can see all the traffic on your local network destined for to the Internet. That is why we need to configure it on the firewall, rather than a local pc.
QOS won't help everyone trying to play MWO, which I hinted at in an earlier post.
Edited by knnniggett, 28 December 2012 - 03:31 PM.
#14
Posted 07 January 2013 - 03:12 PM
Stickjock, on 31 October 2012 - 11:07 AM, said:
TCP 45464
UDP 21000 to 30000
These ports are still correct, and they connect over two different IP addresses, 70.42.29.74 and 70.42.29.75. The TCP ports don't include 45462 or 45463, we use only 45461 and 45464. The TCP ports are for backend server communications, things like logging in, interacting with mechbay, chat. The UDP ports are used for realtime match traffic to the dedicated servers when you're in-game.
#15
Posted 07 January 2013 - 08:34 PM
Google how to use QoS.
Edited by BerryChunks, 07 January 2013 - 08:41 PM.
#16
Posted 08 January 2013 - 05:52 AM
BerryChunks, on 07 January 2013 - 08:34 PM, said:
Google how to use QoS.
Well, yes and no. You are right. Most of us only have the ability to shape outgoing packets. However, that doesn't mean someone else's download activity will not ever affect what you are doing. It certainly can.
Many applications consume upload bandwidth, even when they are "downloading". This is because TCP requires acknowledgement, ack, packets to be sent back to the sender. If you have an asynchronous internet connection (i.e. your upload b/w is much less than your download) the potential problem is made much worse... If your upload bandwidth is consumed by TCP acknowledgement packets (say from someone downloading a large file over http) then your download connection will appear to be choked. If you are playing MWO at the time then you will notice the effects.
Keep in mind that, even though much of MWO uses UDP, not TCP, it is still competing with everything else on your network, TCP, UDP, or otherwise. This is where QOS can come into play in some circumstances. For me, I need it, but I've got a lot of stuff on my network. For others, it may be more complicated than it is worth.
EDIT: The usual spelling and grammar
Edited by knnniggett, 08 January 2013 - 05:55 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users