The master server problems seen on this list from people using NAT-based routers stem from an incorrect outbound NAT configuration.
In basic terms, most NAT routers will modify the source port of an outgoing connection. For example, your server's source port of 27015 will be reported as something else (e.g. 35113) to the master servers. So, your server is technically on the master list, but it has the wrong port. This is why you can't find it. I'm using a FreeBSD-based NAT router for my servers. It's called m0n0wall: http://m0n0.ch/wall/ It gives me the ability to turn off outbound NAT port mapping: http://nyfiber.net/outbound-nat.jpg Unlike me, however, a real server operator would give the public IP directly to the game server and put an enterprise-level firewall in front of it. Cheers, - Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Munoz Sent: Tuesday, September 25, 2007 2:27 PM To: [email protected] Subject: RE: [hlds] Running behind a firewall, getting the external IP to register.... This is my problem too... People can connect and play just fine but the Steam Master Server List just ignores our servers... I do know for a fact it is a firewall issue. The NAT translation is doing something to the packets. Not all firewalls cause this problem when doing NAT. I just wish there was a solution to this besides a new firewall... Mike ParaDOX www.paradisesgarage.com _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
