Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Mar 2004 13:07:58 +0100
From:      Brad Knowles <brad.knowles@skynet.be>
To:        Gleb Smirnoff <glebius@cell.sick.ru>
Cc:        freebsd-net@freebsd.org
Subject:   Re: My planned work on networking stack
Message-ID:  <p0600200ebc6a27773c31@[10.0.1.3]>
In-Reply-To: <20040302082625.GE22985@cell.sick.ru>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
At 11:26 AM +0300 2004/03/02, Gleb Smirnoff wrote:

>    Is there any plans about integration of BGP routing daemon (Zebra or
>  Quagga) into FreeBSD? With BGP routing daemon onboard, FreeBSD will be
>  a strong alternative against expensive commercial routers. I have
>  successfull experience of running FreeBSD STABLE with 2 full BGP views
>  for half a year. Modern i386 PC can route/filter/shape much more traffic
>  than expensive Cisco 36xx. I haven't yet compared with 7000 series...

	Talk to people who have real-world experience in running 
zebra/quagga in ISP environments with multiple upstreams and taking 
full views.  The guy who is designing bgpd for OpenBSD gave a talk on 
the subject at FOSDEM, and it was very enlightening to hear about the 
problems with zebra (which went commercial and the open source 
version basically hasn't been touched in years) and quagga (which is 
a community of zebra users trying desperately to fix the worst of the 
bugs), and how he has used this information during his design of a 
replacement, and the methodology he used to make sure that the 
resulting system is robust and capable of being used in real-world 
production environments.

	His only issue with using exclusively PC equipment for handling 
routing is all those strange WAN protocols and cards for which 
hardware cards are rarely available beyond vendors like cisco or 
Juniper.  That's why he's going pure Ethernet protocols/hardware 
throughout all his networks, including his upstream feeds, so that he 
can dump all that expensive ancient legacy routing hardware.


	If anything, I'd be inclined to look towards his work for OpenBSD 
and see if that could be imported into FreeBSD (and maybe improved, 
with contributions given back to him), rather than mess around with 
crap like zebra or quagga.


	Oh, and it would be nice if someone somewhere started thinking 
about a mesh routing implementation for *BSD, either AODV or 
something else.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"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(+++)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0600200ebc6a27773c31>