15 replies to this topic

[GateKeeper York]

Since the patch this week I have been getting huge packet loss - game not been playable.

Turns out my router (DrayTek) thinks that MWO is a DoS attack.
All is fine if I turn of the UDP Dos threshold.

Can someone advice a value that might work in packets per second?

Quite frustrated that support pointed the finger at reinstall needed then closed the call and refuse to comment on what had changed in the Netcode as mentioned in the patch notes.

Edited by GateKeeper York, 23 May 2013 - 08:36 AM.

[R O C K E T]

Thanks, this fixed it for me too..

[Dalziel Hasek Davion]

I was having the same problem, using a DrayTek 2700 router, switched off the DOS protection on UDP protocols and successfully played my first match since the 21st May - many thanks!

[TELEFORCE]

Does anyone know how to get MWO to work with a D-Link router?

[KurtSture]

Teleforce, you can always monitor the traffic and forward the ports.

[TELEFORCE]

I'll give port forwarding a try. I don't know which ports MWO uses though.

[Tarl Cabot]

TELEFORCE, on 24 May 2013 - 09:31 AM, said:

Does anyone know how to get MWO to work with a D-Link router?

What model of D-Link router? For many of the newer routers, they have a secondary software firewall, aka SPI or stateful packet inspection. Disabling this will generally fix what is blocking the game. It does not disable the hardware, the NAT of the router.

[TyR]

I tested a drop with SPI disabled on my D-Link and crashed back to mechlab before the power up sequence had finished.

[TELEFORCE]

Tarl Cabot, on 24 May 2013 - 03:20 PM, said:

What model of D-Link router? For many of the newer routers, they have a secondary software firewall, aka SPI or stateful packet inspection. Disabling this will generally fix what is blocking the game. It does not disable the hardware, the NAT of the router.

Forgot to mention that. It's a DIR-655 Wireless N Router.

[561st Sith]

Opus posted these on another thread.

TCP 45461
TCP 45464
UDP 21000 to 30000

Hope those help.
S!

561st Sith

[Tarl Cabot]

TyR, on 24 May 2013 - 05:39 PM, said:

I tested a drop with SPI disabled on my D-Link and crashed back to mechlab before the power up sequence had finished.

Is the computer connected via wireless? If so have you tried a direct cord connection?

[Tarl Cabot]

TELEFORCE, on 26 May 2013 - 05:21 AM, said:

Forgot to mention that. It's a DIR-655 Wireless N Router.

What version is it?

http://www.dlink.com...outer?revision=

[TELEFORCE]

Tarl Cabot, on 26 May 2013 - 03:59 PM, said:

What version is it?

http://www.dlink.com...outer?revision=

Revision B

[TELEFORCE]

Alright, I have no idea how to fix this. I've tried port forwarding, but now I start dropping out just before the match begins. The first two times I dropped out to the mechlab. The third and fourth times I dropped to the login screen.

I don't feel that I should have to fix this myself, since this was working fine before the May 21st update. Something's very screwy with MWO.

Edited by TELEFORCE, 31 May 2013 - 06:03 AM.

[Tarl Cabot]

Ok, Version B. Do you have the manual for it? If not use the above link to download it to your computer.

If you are not, are you able to connect via ethernet port? You will need to do this to ensure a solid and consistent connection.

Are you able to log into the router?

DIR-655 Default IP: 192.168.0.1

DIR-655 Default Password:

DIR-655 Default Username:

If you have not changed it it is either admin and no / blank password

On the side bar, click on Firmware - this will bring up a page that will tell you what firmware version you have.

**********************
Ok, for the Dlink router, you will be disabling the SPI (stateful packet inspection)

On the left side, click on Firewall. Uncheck the Enable SPI and hit Save.

This disables the software firewall that is in the router but it does not disable the NAT hardware. SPI has been a pita for many years, particularly with multiplayer games.

[Tarl Cabot]

http://mwomercs.com/...number-for-qos/

The above is link showing the port numbers and IP addresses.

Quote

TCP 45461
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.

Karl Berg

Edited by Tarl Cabot, 01 June 2013 - 08:33 AM.