Doing that causes the server initialization to fail, as it can't bind to the external ip because it doesn't exist on the server.
On Dec 10, 2009, at 12:16 PM, Andrew Leach (luaduck) wrote: > Command line option: +ip x.x.x.x (could be -ip) > > Your server won't show up on the Master Server list if you're viewing it > from the same IP because Gabe knows that you're trying to cause an > infinite loop. > > On 10/12/2009 20:10, Jerod Bennett wrote: >> Hey gang, >> >> I'm sure this has been asked before, but googling just isn't helping me out. >> >> I have a new TF2 server up. You can see that it is available via this link. >> >> http://www.game-monitor.com/search.php?search=jerry >> >> However, it doesn't show up in the Steam Server List. I'm pretty sure this >> is because the server is behind a Firewall, but I thought I'd ask for any >> tips here. >> >> The server has a local IP of 10.10.10.10 and an external IP of >> 70.169.247.109. My firewall is doing a 1 to 1 IP route for this server in >> our DMZ so any traffic to that external IP is directly routed to the local >> IP. >> >> So is there a way for my server to inform the master servers that it is >> really on it's external IP? >> >> Thanks for your time. >> >> -Jerry >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds >> > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
