* Jacques Gelinas ([EMAIL PROTECTED]) wrote:
> $ /sbin/ip addr add 192.168.0.0/24 dev eth0
> $ /sbin/ip addr add 192.168.0.1 dev eth0
> $ /sbin/ip addr add 192.168.0.2 dev eth0
> $ /sbin/ip addr list
>
>
> inet 192.168.0.0/24 scope global eth0
> inet 192.168.0.1/32 scope global eth0
>
On Fri, 31 Oct 2003 10:05:02 -0500, Chris Wright wrote
> * Jacques Gelinas ([EMAIL PROTECTED]) wrote:
> > The ip command uses the same kernel interface as ifconfig to setup IP aliases.
> > The SECONDARY flag can't be touched using the kernel interface.
> > So the command will produce the same probl
On Fri, 31 Oct 2003 10:01:01 -0500, =?iso-8859-1?q?Asbj=F8rn=20Sannes?= wrote
> On Thursday 30 October 2003 17:43, Jacques Gelinas wrote:
>
> > Whenever the kernel drop a "main" IP aliases, all the related (secondary)
> > IP aliases (same network) are also dropped.
>
> A quick workaround would be
* Jacques Gelinas ([EMAIL PROTECTED]) wrote:
> The ip command uses the same kernel interface as ifconfig to setup IP aliases.
> The SECONDARY flag can't be touched using the kernel interface.
> So the command will produce the same problem.
>
> While the ip command do more, especially on the routin
On Thu, 30 Oct 2003 20:44:02 -0500, Herbert Poetzl wrote
> On Thu, Oct 30, 2003 at 11:43:34AM -0500, Jacques Gelinas wrote:
> > Another solution would be to change the kernel. For example, when we delete the
> > main IP alias of a network, instead of deleting the other, we remove the SECONDARY
> >
On Thursday 30 October 2003 17:43, Jacques Gelinas wrote:
> Whenever the kernel drop a "main" IP aliases, all the related (secondary)
> IP aliases (same network) are also dropped.
A quick workaround would be to put up a dummy alias first maybe? I myself
don't remove the aliases when the vserver
torsdag 30. oktober 2003, 17:43, skrev Jacques Gelinas:
> You create a bunch of vserver, all using an IP (or more) address of the
> same IP network. This is fairly common (typical in fact). Say you have the
> following vservers
>
> A: 192.168.0.1/255.255.255.0
> B: 192.168.0.2/255.255.255.0
> C: ..
On Thu, Oct 30, 2003 at 11:43:34AM -0500, Jacques Gelinas wrote:
> Yesterday I stepped on an old behavior of the kernel I was not aware of. I wonder
> if other have experienced the problem it is causing to vservers. Here is what it
> does.
>
> You create a bunch of vserver, all using an IP (or mor
Yesterday I stepped on an old behavior of the kernel I was not aware of. I wonder
if other have experienced the problem it is causing to vservers. Here is what it
does.
You create a bunch of vserver, all using an IP (or more) address of the same IP
network. This is fairly common (typical in fact).
