Date: Wed, 16 Apr 2008 15:06:29 -0400 From: "Zaphod Beeblebrox" <zbeeble@gmail.com> To: "Li, Qing" <qing.li@bluecoat.com> Cc: "M.S. Motanu" <miauris@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: Multipath routing - failover version Message-ID: <5f67a8c40804161206r4273cbb2sb42f478ca0d3d4fc@mail.gmail.com> In-Reply-To: <B583FBF374231F4A89607B4D08578A438C8A6C@bcs-mail03.internal.cacheflow.com> References: <1dd0a33d0804160337o3090ac08g4a2cbc3be0d58b19@mail.gmail.com> <B583FBF374231F4A89607B4D08578A438C8A6C@bcs-mail03.internal.cacheflow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 16, 2008 at 1:38 PM, Li, Qing <qing.li@bluecoat.com> wrote: > I recently incorporated multipath support into -CURRENT, > for the upcoming 8.0. This patch originated from the KAME > The most annoying feature of the -stable routing is that you cannot add an IP to an interface if the route already exists. An example would be our datacentre where two routers both have vlan interfaces on the same subnet and they run OSPF (quagga). If machine you add the IP to the vlan on machine A, you need to stop OSPF on machine B before it will allow you to add the IP on it's vlan. Operationally, this is suboptimal. Is this gnat fixed? Obviously, also, a machine should prefer it's own interface routes to routes provided by external routing protocols. Is anyone involved in this pushing these changes into quagga?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5f67a8c40804161206r4273cbb2sb42f478ca0d3d4fc>