From: Martin List-Petersen (martin_at_list-petersen.dk)
Date: Sun 30 Mar 2003 - 17:38:00 BST
Actually I found the problem on my own ... i had configured all ip's as
aliases before i implemented vserver and not thought of, that the
vserver package would try to "recreate" these aliases.
So removing the eth0:0 -> eth0:x aliases helped and everything works
On Sun, 2003-03-30 at 18:15, Martin List-Petersen wrote:
> i seem to have a odd problem:
> My vservers doen't seem to be bound to only access their own ip-adress.
> When i enter a vserver with: vserver servername enter
> it gives me the following output:
> SIOCSIFBRDADDR: Cannot assign requested address
> SIOCSIFFLAGS: Cannot assign requested address
> ipv4root is now x.x.x.x
> New security context is 12
> So it seems, that i maybe missed something during compile of the kernel
> (am I right here ?)
> The machine is running Debian Woody, kernel 2.4.20ctx-16, vserver
> package 0.22-7 and was a fresh install. On my other server (running
> Debian Woody, kernel 2.4.19ctx-15, vserver package 0.21-1) i don't have
> that problem at all.
> What also happens is that for example exim inside a vserver also binds
> ip's which it doesn't has access to (besides .. all vserver have
> CAP_NET_RAW capability)
> What can i do to find out, what i missed ? Any hints ?
-- Regards, Martin List-Petersen martin at list-petersen dot dk -- Manly's Maxim: Logic is a systematic method of coming to the wrong conclusion with confidence.