You're not accidentally doing anything like not letting udp packets
*out* through the firewall, are you? Perhaps on the LAN link, since
obviously the WAN link appears to be set to allow everything (provided
there aren't any other rules accidentally treading on it).
I guess my question for y
The server has a WAN IP, but has his traffic filtered by the openbsd box.
Since it is not a nat configuration, there is no need to redirect the
packets, just allow them to pass.
I would like to add that all the other services installed work fine :
apache, ftp, postfix, etc, which really points to
On Thu, 18 Dec 2008, Simon Marchi wrote:
> # 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
Are you trying to designate your external ip with the +ip option? It is
a bit counterintuitive, but my experience is, if you are behind a router
or a gateway, you need to designate your internal lan ip, and then it
will work and show up on the Steam server list as it should.
ie. "+ip 192.168.
-Life dedicated Linux server mailing list
Subject: Re: [hlds_linux] Team Fortress 2 server binding to 127.0.0.1...
Same thing.
Well, even with +ip the server understands that I want him to bind to this
IP. It just can't connect to steam server afterwards...
It is really strange...
On Thu, D
Check your /etc/hosts file and correct it.
> Same thing.
>
> Well, even with +ip the server understands that I want him to bind to this
> IP. It just can't connect to steam server afterwards...
>
> It is really strange...
>
> On Thu, Dec 18, 2008 at 4:04 AM, Gary Stanley
> wrote:
>
>>
>> At 02:
-Life dedicated Linux server mailing list
Subject: Re: [hlds_linux] Team Fortress 2 server binding to 127.0.0.1...
Same thing.
Well, even with +ip the server understands that I want him to bind to this
IP. It just can't connect to steam server afterwards...
It is really strange...
On Thu, D
Same thing.
Well, even with +ip the server understands that I want him to bind to this
IP. It just can't connect to steam server afterwards...
It is really strange...
On Thu, Dec 18, 2008 at 4:04 AM, Gary Stanley wrote:
>
> At 02:01 AM 12/18/2008, Simon Marchi wrote:
> >Hi,
> >
> >I am running
At 02:01 AM 12/18/2008, Simon Marchi wrote:
>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
>
At 02:01 AM 12/18/2008, Simon Marchi wrote:
>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
>
; 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:
>
&g
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 her
12 matches
Mail list logo
