Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Aug 2011 01:52:54 +0400
From:      Gleb Smirnoff <glebius@FreeBSD.org>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        net@FreeBSD.org
Subject:   Re: new CARP implementation
Message-ID:  <20110811215254.GX43567@glebius.int.ru>
In-Reply-To: <CAOjFWZ5rq%2B9gYh_Z4uoGj4v6GEJrsXiJepzQn_CogLbDasxhuQ@mail.gmail.com>
References:  <20110810160526.GO43567@FreeBSD.org> <CAOjFWZ7eAME34-zFe7ateDmRmkqWi2Bdow%2Bg4QE_Msa2phCWiQ@mail.gmail.com> <20110811082531.GR43567@glebius.int.ru> <CAOjFWZ5rq%2B9gYh_Z4uoGj4v6GEJrsXiJepzQn_CogLbDasxhuQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 11, 2011 at 02:47:08PM -0700, Freddie Cash wrote:
F> > On Wed, Aug 10, 2011 at 09:38:04AM -0700, Freddie Cash wrote:
F> > F> However, I'm not sure I understand the reasoning for removing the carpX
F> > F> pseudo-interface.  It's really nice having the symmetry between carpX,
F> > F> vlanX, brX, and other pseudo-interfaces, and keeping the configuration
F> > F> details separate from the underlying physical interface.
F> > F>
F> > F> This now makes creating/configuring CARP different from
F> > creating/configuring
F> > F> VLANs.  :(
F> >
F> > This is done because VLANs _are_ interfaces, they are tunnels within
F> > ethernet
F> > interfaces, splitting one interface into a bunch. Bridges are interfaces,
F> > as
F> > well as LACP trunks (lagg(4)), since they group a number of interfaces into
F> > one. CARP addresses _are not_ interfaces, they are addresses. IMHO,
F> > implementing
F> > them as virtual interface subtly attached to a real one, was a layering
F> > violation.
F> >
F> > Thinking about it some more, and doing some reading on how VRRP and CARP
F> work, I'm starting to see things from your point of view.
F> 
F> Now you just need to figure out a way to make ifconfig(8) show which IPs on
F> an interface are controlled via CARP.  Perhaps add it to the carp: line as
F> well?  Or make the carp: a multi-line option?  Or something along those
F> lines?

The problem isn't with printf() layout unfortunately. The problem is that
current interface between kernel and userland, that retrieves list of
addresses on interface doesn't support passing vhid. Interface between
libc and ifconfig neither.

Problem is being worked on. I am now waiting for opinions from several
developers.

-- 
Totus tuus, Glebius.



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