Subject: Re: [vserver] Network changes between guest hosts from 2.2.0.7 to 2.3.0.34?
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Thu, 19 Feb 2009 00:33:14 +0100

On Mon, Feb 16, 2009 at 09:33:09AM +0100, Markus Fischer wrote:
> Hi,
> 
> Herbert Poetzl wrote:
> >>I observed that prior processes bound to 127.0.0.1 were accessible 
> >>from the guests IP, too and this seems to have changed after I 
> >>upgrade to 2.3.0.34.
> >
> >depends on the config (i.e. SINGLE_IP special casing
> >and loopback isolation setup)
> >
> >at kernel configure time, you get presented with
> >some new options (when switching from 2.2 to 2.3)
> >and the accompanied help texts explain their
> >functionality ...
> 
> Ok, I understand. I actually compiled the kernel a year ago and 
> activated it over the weekend, no wonder I didn't remember that option, 
> but you're right, it's activated.
> 
> It causes some issues at the moment which should be fixable. If they
> cause too much trouble, is there a way to deactivate this behavior at
> runtime? Re-start of a vserver would be ok. In other words: to get
> rid of the feature, do I need to recompile the kernel again with this
> option deactivated or is there another way to disable it?

you can disable it with ~single_ip in nflags (config)

HTH,
Herbert

> Lesson learned: don't install a kernel you compiled almost a year ago.
> 
> thanks,
> - Markus