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 you; are there any keep-state rules on the  
traffic coming in, that make the other services you listed off work  
correctly, but would prevent hlds from initiating a connection out?   
Again, I imagine they would have to be on the LAN link.. but if you're  
like me, you simply have a rule on the lan link to pass everything.

-Joe

On Dec 18, 2008, at 1:26 PM, Simon Marchi wrote:

> 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 something like a bad
> network configuration directly on the server that hlds doesn't like...
>
> Thanks for your help!
>
> On Thu, Dec 18, 2008 at 10:41 AM, kama <[email protected]> wrote:
>
>>
>>
>> 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 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 :)
>>
>>

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to