From owner-freebsd-current@FreeBSD.ORG Tue Mar 2 05:40:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04D9116A4CF; Tue, 2 Mar 2004 05:40:13 -0800 (PST) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E410D43D2F; Tue, 2 Mar 2004 05:40:11 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.3] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id i22Ddrxe001412; Tue, 2 Mar 2004 08:39:55 -0500 (EST) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@127.0.0.1 Message-Id: In-Reply-To: <20040302090219.GC3438@astral-on.net> References: <4043B6BA.B847F081@freebsd.org> <200403011507.52238.wes@softweyr.com> <20040302031625.GA4061@scylla.towardex.com> <20040302042957.GH3841@saboteur.dek.spc.org> <20040302082625.GE22985@cell.sick.ru> <20040302084321.GA21729@xor.obsecurity.org> <20040302090219.GC3438@astral-on.net> Date: Tue, 2 Mar 2004 14:36:50 +0100 To: ad@astral-on.net From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: My planned work on networking stack X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 13:40:13 -0000 At 11:02 AM +0200 2004/03/02, Andrew Degtiariov 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? Maybe there's nothing you can do about this last item, but there's plenty that can be done on the software side -- just take a look at all the protocols that have been identified as being desirable, but not yet implemented by zebra/quagga. Oh, and then there are all the operational issues where zebra/quagga can't keep sessions going when a neighbor flaps, etc.... Those would require re-architecting the whole routing system, at which point it might make a lot more sense to go with a different implementation -- such as bgpd from OpenBSD. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)