Ok, I've been able to at least start my servers and are working fine.
To sort the 127.0.0.1 issue, just use the old /etc/hosts trick and assign the
ip address you need to the machine hostname. For example, our test server looks
like
192.168.2.101 XGALinux
So srcds will use that IP
--
On Friday 17 December 2004 11:07, PiTaGoRaS wrote:
[...]
To sort the 127.0.0.1 issue, just use the old /etc/hosts trick and assign
the ip address you need to the machine hostname. For example, our test
server looks like
192.168.2.101 XGALinux
So srcds will use that IP instead of
Do I need to edit the localhost ip or add another line ? TIA
B
- Original Message -
From: PiTaGoRaS [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 17, 2004 10:07 AM
Subject: Re: [hlds_linux] RE: [hlds] Counter-Strike Source update (temp fix)
Ok, I've been able to at least
That's why I warned about multihomed servers. If you have only one public
interface per server, that would do the trick.
--
PiTaGoRaS
Mariusz Zielinski escribió (Fri, 17 Dec 2004 13:16:34 +0100):
--
On Friday 17 December 2004 11:07, PiTaGoRaS wrote:
[...]
To sort the 127.0.0.1 issue, just
10:07 AM
Subject: Re: [hlds_linux] RE: [hlds] Counter-Strike Source update
(temp fix)
Ok, I've been able to at least start my servers and are working
fine.
To sort the 127.0.0.1 issue, just use the old /etc/hosts trick and
assign the ip address you need to the machine hostname. For
example
Of PiTaGoRaS
Sent: 17 December 2004 12:57
To: [EMAIL PROTECTED]
Subject: Re: [hlds_linux] RE: [hlds] Counter-Strike Source update (temp fix)
That's why I warned about multihomed servers. If you have only one public
interface per server, that would do the trick.
--
PiTaGoRaS
Mariusz Zielinski escribió (Fri
6 matches
Mail list logo
