Subject: Re: [vserver] strange network issues
From: Corin Langosch <corinl@gmx.de>
Date: Sat, 21 Feb 2009 19:47:42 +1300

On 21.02.2009 15:27, ben@bristolwireless.net wrote:
> Quoting Corin Langosch <corinl@gmx.de>:
>> Is this a know issue with the release I'm using? Anyone faced the same
>> weierd problem and found a solution? May be the solution is to always
>> define a "lo" interface too (is this a new requirement?)?
>>
>> Thanks,
>> Corin
> Do you have a net.ipv4.conf.all.promote_secondaries=1 line in
> /etc/sysctl.conf ? If not this might hfix the problem. One can also use
>
> $ sysctl -w net.ipv4.conf.all.promote_secondaries=1
>
> in order set this without rebooting.
No it's not set - what does this flag exactly do? I just read a bit
about it and it seems it only comes into play when the main device (so
eth0?) goes down. I didn't find any syslog entries concerning network
issues, not at the host nor at the guest...so I think eth0 did not
change it's state. Also the host was reachable with the same network
details as always, only all or most of the vserver had lost their ips.
Did this flag change between 2.6.22 and 2.6.26 or between the different
vserver versions?

Corin