Date: Fri, 21 Sep 2007 16:52:05 +0100 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Steve Bertrand <iaccounts@ibctech.ca> Cc: mattr@eagle.ca, freebsd-net@freebsd.org, Sten Daniel Soersdal <netslists@gmail.com> Subject: Re: Quagga as border router Message-ID: <46F3E8A5.6010304@FreeBSD.org> In-Reply-To: <46F3B7C9.7050605@ibctech.ca> References: <46F1AC0B.9040109@ibctech.ca> <46F1BDE1.8090102@gmail.com> <46F1F136.3010203@ibctech.ca> <46F23D74.9000701@gmail.com> <46F3B7C9.7050605@ibctech.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Folks have been asking about XORP in this thread.
XORP can take a full BGP feed just fine as long as you have enough
memory.; for a full default-free-zone feed, you are looking at in the
region of 1GB - 1.5GB, perhaps less if you use aggregation.
If you look at the NSDI '05 paper you'll see that it has a number of
benefits over existing designs, BGP route propagation in particular
should be faster:
http://www.usenix.org/events/nsdi05/tech/handley.html
The architecture is deliberately structured so that forwarding
functionality may be implemented in hardware. I believe XORP may work
with the NetFPGA but don't have firm information about this.
IPv6 support is strong as XORP was designed to route IPv6 from the start
as a whole suite - multicast support is also strong.
regards,
BMS
[Note: my opinion may be biased as I served on XORP core team for a few
years, and still actively contribute code to the project.]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46F3E8A5.6010304>