Date: Tue, 2 Mar 2004 11:43:40 -0800 (PST) From: Mike Hoskins <mike@adept.org> To: net@freebsd.org Cc: current@freebsd.org Subject: Re: My planned work on networking stack Message-ID: <20040302113821.S53840@snafu.adept.org> In-Reply-To: <p06002016bc6a3d9b6c9c@[10.0.1.3]> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302084321.GA21729@xor.obsecurity.org> <p06002016bc6a3d9b6c9c@[10.0.1.3]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Mar 2004, Brad Knowles wrote: > > What's difference (*currently*) beetwen FreeBSD+Zebra and Cisco routers? > Support for VRRP? Support for various other routing protocols > not covered by zebra/quagga -- at least not yet, if ever? Support > for line cards and other devices that do not exist in a format you > can plug into a PC? actually, there's a lot of differences at the hardware level (beside available interfaces) -- some of which will probably always be there (on any platform). just post this question to nanog, and wait for your inbox to be flooded. (yes, hard to believe, but there really are technically justifiable reasons a lot of big names use hardware engineered for the task of routing beside paying ridiculous fees to the vendors.) as for vrrp, there is an opensource/RFC-compliant implementation that works on FreeBSD. actually, it was coded specifically for FreeBSD. http://freshmeat.net/projects/freebsd-hut i have never used this on a large-scale (i've never considered pre-1.0 software "stable"), but have used it many places for failover inside clusters with satisfactory results. -m
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040302113821.S53840>