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

To: 500888@bugs.debian.org
Subject: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
From: Holger Levsen <holger@layer-acht.org>
Date: Thu, 2 Oct 2008 14:13:06 +0200
Message-id: <[🔎] 200810021413.07887.holger@layer-acht.org>
Reply-to: Holger Levsen <holger@layer-acht.org>, 500888@bugs.debian.org
In-reply-to: <[🔎] 20081002111442.9107.60451.reportbug@caffeinated>
References: <[🔎] 20081002111442.9107.60451.reportbug@caffeinated>

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? (Or can you access the others 127.0.0.1s from the other 
vservers?


regards,
	Holger

Attachment: pgp_76PuxBuCZ.pgp
Description: PGP signature

Reply to:

References:
- Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
  - From: Matthew Sackman <matthew@wellquite.org>

Prev by Date: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
Next by Date: Bug#500894: linux-image-2.6.26-1-amd64: Broadcom (b43) wireless driver broken
Previous by thread: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
Next by thread: Bug#500888: linux-image-2.6.26-1-vserver-amd64: cannot specify lo as non 127.0.0.1 in vserver guests
Index(es):
- Date
- Thread