Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Oct 2011 23:12:45 +0400
From:      Gleb Smirnoff <glebius@FreeBSD.org>
To:        Andre Oppermann <andre@FreeBSD.org>
Cc:        net@FreeBSD.org
Subject:   Re: new CARP implementation
Message-ID:  <20111014191245.GL94905@glebius.int.ru>
In-Reply-To: <4E988851.3040801@freebsd.org>
References:  <20110810160526.GO43567@FreeBSD.org> <20111013160216.GU94905@glebius.int.ru> <4E9874C5.8070309@freebsd.org> <20111014180205.GG94905@glebius.int.ru> <4E987C0A.2040600@freebsd.org> <20111014184843.GI94905@glebius.int.ru> <4E988851.3040801@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 14, 2011 at 09:06:57PM +0200, Andre Oppermann wrote:
A> > Won't ifconfig it down work?
A> 
A> Not if I want to continue to use the primary or other non-carp address.

Well, the best idea for that case would be switch them to backup mode.
In presense of active master, they won't show up any way either on wire,
neither in the stack.

A> > A>  >  btw, you can configure a VHID and don't attach any addresses
A> > A>  >  to it.
A> > A>
A> > A>  How does that work? What purpose does it serve?
A> >
A> > This is actually how it is configured: SIOCSVH, then SIOCAIFADDR.
A> > There is no practical use in addressless vhid now.
A> 
A> If it can cause problems or non-standard behavior it should not be
A> allowed and the carp status should be suspended until fully configured.

Status of such addressless vhid is always INIT, so it causes no activity
either on wire or in stack :)

A> One more question: Can one interface with multiple addresses become a
A> member of different carp groups (with a different address each)?

Sure. All imaginable options are configurable: arbitrary number of
addresses on interface, arbitrary number of vhids on interface,
arbitrary number of addresses configured to a particular vhid.

-- 
Totus tuus, Glebius.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111014191245.GL94905>