PfSense + multiple MW2 clients..

BrainEater

[H]ard|Gawd
Joined
Jul 21, 2004
Messages
1,216
Ok , I run a PfSense router ( v1.2 rc4).

I have set my main rig as a static IP , and opened both a) the required incoming ports and , b) the outgoing ports (outgoing PAT is essentially disabled.) , for Modern Warfare 2 to run correctly.

It works perfectly , MW2 reports NAT as open.Everything is peachy.

The problem arose when my friend came over with his rig.

I set him with a static IP.This functions correctly.
When I give him the exact same ruleset I use for the main rig (the IP is different of course) it won't work.MW2 reports the NAT as 'strict'.....now this is only an issue because we can't seem to play on the same party.It won't let us , we both need to be 'open'.

I've checked the NAT/firewall rulesets several times.They seem to be correct, it should work.I know I can open ports on his computer , his uTorrent works perfectly...I have no idea why MW2 won't work.

Am I missing something ?

Any Ideas ?

tyia :D
 
Try switching to advanced outbound NAT and checking the 'static port' option in the auto-generated outbound rule that should be there.
 
Yep , thats already done.

It works perfectly for my computer.It's the second machine that won't go.
 
Are you sure the protocol is designed in such a way that it can have multiple clients behind the same IP?
 
Are you sure the protocol is designed in such a way that it can have multiple clients behind the same IP?

In the OP he said he put the 2nd machine on a static ip so I assume they are on separate ips.
 
In the OP he said he put the 2nd machine on a static ip so I assume they are on separate ips.

I believe the OP was referring to statically assigning a private IP from his home network to each of the two systems. I also believe Keenan was inquiring as to whether or not the protocol can have multiple clients behind a single public IP.

Could be wrong on either count, but I believe that was what both of them are talking about!

As to whether or not it can be done, two of my friends play MW2 in the same household on two 360s. I have no experience with the PC version.
 
You will need to delete your custom rules for both xbox's, give each xbox 360 a dhcp reserved address, and enable UpNP on the lan interface. Works like a charm. Not the absolute safest thing in the world to enable UPnP (A virus could very well open a port too), but hey, take it up with Microsoft.
 
UPnP should do it...even just a single PC behind PFSense, it'll run fine without opening/fowarding ports...you won't get the NAT error. My son played that game for quite a while, I never opened/forwarded ports or did anything specific for it on my PFSense box.
 
I believe the OP was referring to statically assigning a private IP from his home network to each of the two systems. I also believe Keenan was inquiring as to whether or not the protocol can have multiple clients behind a single public IP.


Yep.

I don't know if it can.That's a good question.

-------

While yes, mw2 will run behind pfsense without opening ports , it does so in 'strict' NAT mode ; what this means, is you will never host games.

Also , it's mw2 for the PC , not xbox.

-----

If UPnP works , I should be able to manually setup the router to do the same thing , without the associated risks of UPnP.

hmmmmm.....

:D
 
"Hosting games"...yes...you'd want to open/forward ports for that, so that people "across the internet..outside of your home network"...can connect to your game server services. But port forwarding is unrelated to outgoing traffic, opening/forwarding ports is not needed when you play out in the internet.

I cannot imagine they'd revert their game engine back to years ago...when many games wouldn't support multiple clients behind the same IP address. Meaning..if you have 2x people playing the game...from the same network, out on a public game server..the public game server sees both of your traffic as coming from the same IP address. Your routers WAN IP. Many years ago many games had this problem. Quake 1, Quake 2. Quake 3 got rid of that problem...it no longer exists, we often played on the same public server in that game. I recall Call of DooDoo games being based on the Quake engines.

//ponders for a minute...
Actually based on a Google search...this may be the path..if a server isn't setup correctly to deal with this
http://www.fpsadmin.com/forum/showthread.php?t=13888
 
UPnP works because the xbox automatically chooses DIFFERENT ports and then opens them on the router. You can't tell the xbox manually to use non standard xbox live ports. Yes, it's stupid. Unless you have a static public ip per xbox and do 1:1 nat, you'll have to use UPnP for "true" open nat on each xbox.
 
So are you statically forwarding all the incoming ports to your main machine?
 
He's playing the PC version of MW2, which doesn't have dedicated servers but rather one of the players in the match "host" the game. I'm not sure if UPnP is capable of allowing "hosting" to happen, is it?
 
... Damnit, someone should have corrected me sooner that he was using the PC version. I have no idea where I pulled xbox from.

In the link you use to launch the game add "+set net_port 28960" to the first one and forward the port to that pc. Do the same thing to the other guy's pc and add +set net_port 28961 and forward that port to his pc. Don't use port ranges, just forward the single port tcp/udp.

If for whatever reason the above doesn't work for you, UPnP works with the pc version to.
 
I cannot imagine they'd revert their game engine back to years ago...

ahahahahhahahahaha *wheeze* hahahahahahha

:p

I won't go off into a rant about the issues with mw2....really fun game , kinda annoying at times.... :rolleyes:

Yea it's on the quake4 engine.

-----------------

//ponders for a minute...
Actually based on a Google search...this may be the path..if a server isn't setup correctly to deal with this
http://www.fpsadmin.com/forum/showthread.php?t=13888

-

...

In the link you use to launch the game add "+set net_port 28960" to the first one and forward the port to that pc. Do the same thing to the other guy's pc and add +set net_port 28961 and forward that port to his pc. Don't use port ranges, just forward the single port tcp/udp.

Very cool , Thanks a lot guys !! I will try that.

mw2 doesnt use a port range.It uses 28960.......Can I assume 'IWnet' will recognize the 28961 machine ?

I'll try it either way !

:D
 
Dammit !!

It still does not work.

Good try tho.mw2 strikes again I guess.

Here's how I have the router set right now :

mw2rout1.jpg


----

The first 5 entries are my main rig , using the +set_netport 28960 on the launch icon.

It works perfectly , mw2 reports nat as 'open'.

The second 5 entries are my friends rig , using +set net_port 28961 on the launch icon.

His mw2 still reports the NAT as 'strict'.

:(

Thoughts ?

:D
 
That port trick worked with cod4, oh well.

Seriously dude, with all the good UPnP will do for you, it outweighs the minor possibility of you getting a virus that can harness UPnP.
 
Yep I will give UPnP a try .

Couple of questions about this tho :

-Should I leave the port forwards for my rig or just let UPnP handle it all ?

-The UPnP in Pfsense allows you to default deny , then add specific port ranges for 'allow'....what's a good range around 26980 , or do I just open em all ?

Thanks again !

:D
 
Remove your manual port forwards...
And just default enable UPnP service...bind it to the correct interface.

The big UPnP vulnerability was patched back..in like..the XPsp1 days. If you've kept partially up with your windows updates, don't lose sleep over it.
 
Ugh.

Ok , I setup UPnP on the router.

When I run mw2 , it reports the NAT as 'open'......so far so good.

When my friend runs mw2 , it reports NAT as open too...

Here's the issue : whichever machine connects second , gets held up at " connecting to IWNet".......the two will not connect at the same time.

------

I guess I have some research to do.......I laugh if IW made a non-lannable game.

:rolleyes:
 
Hahahah.....

Everything I've seen suggests it is NOT lannable...The are actually 'LAN cracks' out there.

Nice work Activision/InfinityWard....you've fucked it up , AGAIN.

God you guys suck.

---------

Thanks for the help anyways everyone .
 
Back
Top