Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests

2008-10-03 Thread Bastian Blank
On Thu, Oct 02, 2008 at 12:14:42PM +0100, Matthew Sackman wrote: Under 2.6.22-3-vserver-amd64 (and earlier), this all worked fine. Under 2.6.26-1-vserver-amd64 this does not work: every vserver guest is started with lo as 127.0.0.1, thus breaking the internal network badly. 127.0.0.1 is the

Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests

2008-10-02 Thread Matthew Sackman
Package: linux-image-2.6.26-1-vserver-amd64 Version: 2.6.26-6 Severity: important Each of my vserver guests has a separate loopback interface. This is specified as normal in /etc/vserver/$guest/interfaces/. For example, I have: .../1/dev is lo .../1/ip is 127.32.0.1 .../1/prefix is 8 Under

Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests

2008-10-02 Thread Holger Levsen
Hi, On Thursday 02 October 2008 13:14, Matthew Sackman wrote: Under 2.6.22-3-vserver-amd64 (and earlier), this all worked fine. Under 2.6.26-1-vserver-amd64 this does not work: every vserver guest is started with lo as 127.0.0.1, thus breaking the internal network badly. Ain't that a feature?