With as long as this type of behavior has been going on, I would go with option 4, not likely to be implemented. And there was also an update a little earlier today that fixes having a steamgroup exclusive L4D server.
I agree being able to specify to the world what your external IP is would be a treat, as it is now you can tell if someone is running a NAT server via a simple status command in the client console (provided you know all the dedicated private IP ranges). mauirixxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jevon Sent: Monday, November 17, 2008 12:02 PM To: [email protected] Subject: [hlds] External/Public IP, NATing firewall Hi all, Apologies if I've missed a discussion about this somewhere, I've looked many different places and come up blank. I run a DS (specifically L4D) for some friends on my desktop machine. I am behind a router which does NAT so have a private/internal IP (10.0.0.2). Naturally, my friends need my public address, and I make use of dyndns for ease (port forwarding is working fine). I can't see an easy way to get this set up working cleanly but I can't imagine it's a rare configuration. Is it possible to specify separate "external" IPs and internal IPs? If I let the server pick up the IP, it detects 10.0.0.2, as expected, and although people can connect in the console ("connect l4d.dyndns.org" for example) it won't show up correctly anywhere else - people can't browse it in any way (and with sv_password not working at the moment, it's open to anyone as the sv_steamgroup stuff doesn't appear to work either). If I specify my external ip, either on the command line or in my autoexec.cfg, the server starts barfing and doesn't talk to the VAC servers - the following is all that gets shown: ... NET_GetBindAddresses found 10.0.0.2: 'NETGEAR 108 Mbps Wireless PCI Adapter WG311T' WARNING: NET_OpenSocket: bind: WSAEADDRNOTAVAIL Trying to open socket on 10.0.0.2 WARNING: NET_OpenSocket: bind: WSAEADDRNOTAVAIL WARNING: NET_OpenSocket: bind: WSAEADDRNOTAVAIL Trying to open socket on 10.0.0.2 WARNING: NET_OpenSocket: bind: WSAEADDRNOTAVAIL Trying to open socket on 10.0.0.2 Socket bind failed (WSAEADDRNOTAVAIL) Network: IP xx.xx.xx.xx, mode MP, dedicated Yes, ports 27020 SV / 27015 CL ---- Host_NewGame ---- Compact released 131072 bytes to the backing store Host_NewGame on map l4d_dem_hospital01_apartment Executing dedicated server config file Commentary: Could not find commentary data file 'maps/l4d_dem_hospital01_apartment_commentary.txt'. CreateBoundSocket: ::bind returned Win32 error 10049 cminterface.cpp (932) : Assertion Failed: NULL != m_hConnection It looks like the server tries to bind to the external IP, which naturally is assigned to the router, not the computer, so it bugs out (as you'd expect). Ideally, I need to be able to tell the server to bind to the "internal" IP, but publicise a specified external IP (e.g. a new server variable along the lines of external_ip which I could set to either a DNS entry or an IP like with the existing ip variable) to the Steam servers/other users. Obviously there might be a slight issue if other people were on my internal network but it should still play ball connecting to the external IP. Is such a thing: 1) Possible now, just differently 2) Should be possible similar to above but broken 3) Planned but not implemented 4) Unlikely to be implemented Hopefully having written all that it's not going to be something blindingly obvious that I've overlooked and which makes me look like an idiot :-( Cheers, Jevon _______________________________________________ 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
