2005/11/7, Sam Vilain [EMAIL PROTECTED]:
Strange. Certainly in terms of firewalling, packets that don't leave
the host always travel via the loopback interface.
I know, they also screw up netfilter debug messages :)
I'd be curious if the same thing happens without vserver (eg, by just
Yup, that was it! :-)
Are there any plans to make 127.0.0.1 existant in future versions of vserver?
Regards,
Evert
Oliver Welter wrote:
Hi,
I think that this problem is related to the nonexisting 127.0.0.1
address. If I remeber correctly than nagios try to ping this address and
On Tue, Nov 08, 2005 at 10:03:40AM +0100, Evert Meulie wrote:
Yup, that was it! :-)
Are there any plans to make 127.0.0.1 existant in future versions of
vserver?
yes :)
Regards,
Evert
Oliver Welter wrote:
Hi,
I think that this problem is related to the nonexisting
Hi,
The following patch is needed for utsname to be properly supported
on ppc64. Bug was found by testme.sh #031 :)
(This patch is against the 2.6.14-vs2.2 patch)
thanks,
-serge
Index: linux-2.6.14/arch/ppc64/kernel/syscalls.c
On Tue, 8 Nov 2005 13:04:50 +0100, Herbert Poetzl wrote:
On Tue, Nov 08, 2005 at 10:03:40AM +0100, Evert Meulie wrote:
Yup, that was it! :-)
Are there any plans to make 127.0.0.1 existant in future versions of
vserver?
yes :)
Does this mean that binding to 127.0.0.1 is currently risky in
Hi Herbert,
From now on http://linux-vserver.nl is redirecting to
http://linux-vserver.org.
I hope this appreciated. If so, don't include my name on linux-vserver.org.
If you want, you can get linux-vserver.nl on your name and in your
dns-server for free. In that case, I'll hear from you.
