[hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
Hello, I have 8 forked servers running. Two of these servers have sv_search_key and sv_password set in their serverXX.cfg files. However, I am not able to find these servers if I try to join from a lobby. Entering sv_search_key and sv_password into the console of each server shows that these

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
Also, only server #1 shows up in the server browser. Shouldn't I see all 8? This is quite frustrating. Thanks, Dave David A. Parker wrote: Hello, I have 8 forked servers running. Two of these servers have sv_search_key and sv_password set in their serverXX.cfg files. However,

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
I stopped the iptables firewall on the local machine and this fixed the server browser issue. Apparently you need more than the default ports open in order to see all of the forked servers in the server browser. Since I'm connecting from within our network, I would imagine the other servers

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread Fyren
On Fri, Nov 14, 2008 at 15:38, David A. Parker [EMAIL PROTECTED] wrote: I stopped the iptables firewall on the local machine and this fixed the server browser issue. Apparently you need more than the default ports open in order to see all of the forked servers in the server browser. Since I'm

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers in the firewall, though. So does *each* hostport need to be open? Thanks, Dave Fyren wrote: On Fri,

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread Fyren
On Fri, Nov 14, 2008 at 15:53, David A. Parker [EMAIL PROTECTED] wrote: Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers in the firewall, though. So does *each*

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread Milton Ngan
server mailing list Subject: Re: [hlds_linux] Can't connect from lobby Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers in the firewall, though. So does *each* hostport

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
mailing list Subject: Re: [hlds_linux] Can't connect from lobby Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers in the firewall, though. So does *each* hostport

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread David A. Parker
mailing list Subject: Re: [hlds_linux] Can't connect from lobby Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers in the firewall, though. So does *each* hostport

Re: [hlds_linux] Can't connect from lobby

2008-11-14 Thread gameadmin
2008 20:53 To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Can't connect from lobby Perhaps I misunderstood Milton's posts. It sounded to me like only the *first* hostport needed to be open. It didn't make sense to me how this would work without using triggers