Date: Wed, 15 Jun 2005 18:39:19 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: gtg062h@mail.gatech.edu Cc: Yar Tikhiy <yar@comp.chem.msu.su>, freebsd-pf@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: Carp Suppression Message-ID: <20050615143919.GE8060@cell.sick.ru> In-Reply-To: <7c8f2792050613090040c924c3@mail.gmail.com> References: <7c8f2792050610090049064e11@mail.gmail.com> <7c8f279205061116021f55e8da@mail.gmail.com> <7c8f279205061307103b1782f4@mail.gmail.com> <20050613153550.GA54388@comp.chem.msu.su> <7c8f2792050613090040c924c3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 13, 2005 at 12:00:36PM -0400, Josh Kayse wrote: J> The reason we are using CARP on a PLIP interface is to allow us to J> have redundant connections between 2 transparent bridging firewalls. J> Instead of sending packets over our network, we isolate them onto a J> PLIP interface and crossover interface. We then use ifstaded to J> monitor the carp interfaces and shut down bridging on one of the J> machines. AFAIU, you use PLIP line as some flag that triggers suppression. If slave "sees" master via PLIP, it keeps itself in slave mode. May be I don't understand you right. Although the idea is not officially supported, it is interesting. Can you please draw your setup, since I don't understand it clearly? Bringing link state support for p2p interfaces is a TODO, although CARP is not going to be supported on p2p interfaces officially. J> I will refrain from submitting any code to the community in the future. Why? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050615143919.GE8060>