Firewall/NAT

OK guys, I've searched the entire interwebs trying to find a solution and nothing has worked.

I scoured every post for every possible port that Call of Duty: Modern Warfare 2 needs open to be a host and not have "strict" mode listed.

I've got NAT forwarding the following ports to my "Static" IP on my Windows PC... I've verified this by loading an SSH daemon on the PC and changing it to listen to one of the NAT forwarded ports and connecting to it, works fine.

1500
3005
3074-3075
3101
3478-3479
3658
5223
27000-27050
28960-29000


That covers every port I've seen listed.

The firewall rules match to make sure it's not blocking the packets either.

http://www.epicforums.net/img/m0n0-nat-rules.png

http://www.epicforums.net/img/m0n0-fire-rules.png

No matter what I do, it just doesn't work. The sad thing is that users with pfSense don't seem to have this problem (when using uPNP).

What the hell am I doing wrong?

MW2 requires upnp in order to work properly online. Unfortunately Monowall does not supoort it, so you either switch to pfSense or you play something else.

I think most steam games using their net module are affected by that.
Was having the issue with Alien Swarm and tried forwarding ports like crazy.
I think to some extent this is Steam's fault.
What I *think* happens is that outgoing packets still get their port remapped by m0n0wall, even if there is an inbound NAT rule for the same source ip/port combo[1], so other peers will try to reach your client by this remapped port, instead of trying the "official" port first, which would be properly mapped.
So when Steam is trying to determine your firewall type, it should take this into consideration and not brand you as being strict-NATed by not trying the default ports first.
What happens then if the game can't establish direct UDP communication between you and the server, who might also be NATed, is that all you traffic gets routed through a Steam server located in the US, using a STUN server. -> Horrible pings

[1] If this is the case it would be interesting to know if you could disable port remapping just for packets that would match an inbound NAT rule. This *might* be a workaround.

Try this: http://forum.m0n0.ch/index.php/topic,480.0.html#msg6762

You only need to forward UDP 28960 and it should work great.