It should be -ip, not +ip... I'm not sure if that's one of the parameters the server will tolerate the wrong format for or not (+commands are ones that get sent to the server console, rather than startup options to the process)
..OK I just checked and it _is_ one of the ones where it doesn't matter... with either form, as long as I specify the correct public IP I get a secure connection. If I'm reading your firewall rules right (I use iptables personally) that's basically saying allow any TCP or UDP in either direction, yes? That's even more permissive than mine (I have allow all outgoing but only allow established/related incoming) so that shouldn't be an issue. > -----Original Message----- > From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux- > boun...@list.valvesoftware.com] On Behalf Of Simon Marchi > Sent: 18 December 2008 07:01 > To: hlds_linux@list.valvesoftware.com > Subject: [hlds_linux] Team Fortress 2 server binding to 127.0.0.1... > > Hi, > > I am running Debian Etch fully updated on a Core 2 Quad Q8200. I have > installed the TF2 content with the following command: > > ./steam -command update -game tf -dir . > > and it has updated with no problem. I am then trying to run it, with > this > command: > > ./srcds_run -game tf +map ctf_2fort > > And here is the result: > > Auto detecting CPU > Using SSE2 Optimised binary. > Server will auto-restart if there is a crash. > > Console initialized. > Game.dll loaded for "Team Fortress" > Particles: Missing 'particles/error.pcf' > maxplayers set to 24 > Unknown command "startupmenu" > Network: IP 127.0.0.1, mode MP, dedicated Yes, ports 27015 SV / 27005 > CL > ConVarRef room_type doesn't point to an existing ConVar > exec: couldn't exec skill1.cfg > Executing dedicated server config file > Unknown command "sv_client_interpolate" > exec: couldn't exec ctf_2fort.cfg > Adding master server 68.142.72.250:27011 > Adding master server 72.165.61.189:27011 > *status* > hostname: Thetu.bz > version : 1.0.4.4/14 3691 insecure (secure mode enabled, disconnected > from > Steam3) > udp/ip : 127.0.0.1:27015 > map : ctf_2fort at: 0 x, 0 y, 0 z > players : 0 (24 max) > > # userid name uniqueid connected ping loss state adr > Could not establish connection to Steam servers. > > Everything looks fine, except for the network connections. It appears > to > bind itself to the local address instead of eth0. If I try to specify > the IP > with the +ip parameter, get the exact same result, but with the IP > instead > of 127.0.0.1 (I still get the Could not establish connection to Steam > servers error). In both cases, I can't connect to it from a client. > > Both master servers are ping-able from this server. > > It is located behind a OpenBSD/Packet Filter firewall, but I have put > these > rules for testing purpose: > > pass on $uplink_if proto {tcp,udp} from any to $blackmesa keep state > pass on $uplink_if proto {tcp,udp} from $blackmesa to any keep state > > blackmesa -> name of the server :) > > So, if anyone has an idea about how to fix this, thanks for sharing :) > > Simon Marchi > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
