From owner-freebsd-net@FreeBSD.ORG Sun Dec 16 21:31:35 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B343E16A476 for ; Sun, 16 Dec 2007 21:31:35 +0000 (UTC) (envelope-from hhw@astutehosting.com) Received: from defout.telus.net (defout.telus.net [199.185.220.240]) by mx1.freebsd.org (Postfix) with ESMTP id 75EE713C4F0 for ; Sun, 16 Dec 2007 21:31:35 +0000 (UTC) (envelope-from hhw@astutehosting.com) Received: from priv-edtnaa05.telusplanet.net ([154.5.184.6]) by priv-edtnes27.telusplanet.net (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20071216210320.CYFN1467.priv-edtnes27.telusplanet.net@priv-edtnaa05.telusplanet.net>; Sun, 16 Dec 2007 14:03:20 -0700 Received: from [192.168.3.9] (d154-5-184-6.bchsia.telus.net [154.5.184.6]) by priv-edtnaa05.telusplanet.net (BorderWare MXtreme Infinity Mail Firewall) with ESMTP id 9BK4ACKE3D; Sun, 16 Dec 2007 14:03:15 -0700 (MST) Message-ID: <47659291.6050809@astutehosting.com> Date: Sun, 16 Dec 2007 13:03:13 -0800 From: Han Hwei Woo User-Agent: Thunderbird 2.0.0.9 (X11/20071123) MIME-Version: 1.0 To: Niki Denev References: <2e77fc10712132129o810a608v4ec6a742f9860a63@mail.gmail.com> <47625B80.3090904@FreeBSD.org> <2e77fc10712140937i19741f9cwe717499b18012a9a@mail.gmail.com> <2e77fc10712161021x378114eeh8cc0b2e0809800db@mail.gmail.com> In-Reply-To: <2e77fc10712161021x378114eeh8cc0b2e0809800db@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org Subject: Re: is carp on if_bridge possible? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 21:31:35 -0000 Hi Niki, I hope I'm understanding you correctly, but the reason you're running if_lag is so that failover will occur even if there is a switch failure? If you enable preempt by setting: sysctl net.inet.carp.preempt=1, and you have a carp running on the routers' interface that goes through the switches, all the carp interfaces would failover in the event of a switch failure, including the external facing one. With bridging or link aggregation, there is nothing to stop a router from staying the master on the external interface, even if the switch it is connected to fails. Cheers, Han Hwei Woo Niki Denev wrote: > On Dec 14, 2007 12:37 PM, Niki Denev wrote: > >> On Dec 14, 2007 5:31 AM, Bruce M. Simpson wrote: >> >>> Niki Denev wrote: >>> >>>> Hello, >>>> >>>> Is this possible? >>>> I've tried adding IFT_BRIDGE next to IFT_ETHER and IFT_L2VLAN in ip_carp.c >>>> but this probably is not enough. Any ideas? >>>> >>>> >>> CARP is 'special' in that it needs to add its own MAC addresses to your >>> interface, needs a bit of special cooperation between the IP layer and >>> the MAC layer, and it's more than likely that this doesn't work with >>> if_bridge. >>> >>> Like Max says, this is an unusual configuration.... what are you trying >>> to do? >>> >>> BMS >>> >>> >>> >> I'm trying to setup a highly redundant configuration of >> two routers and two rstp capable switches behind them. >> Each of the router is connected to each of the switches, >> and it's two interfaces are part of a bridge group. >> this way i can handle router and/or switch failure without >> disconnecting the site. >> The problem is that this a remote site which must not go offline by >> any means, and thus the unusual setup. >> >> Hope that this explains it. >> >> Niki >> >> > > > Maybe using bridge with rstp for failover was not the best idea, and i > switched to if_lagg > and if_carp on top of it. > It seems to work properly and is exactly what i wanted to achieve. > > Thanks, > Niki > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > >