Hello,
Anybody working with Quagga for production peering with multiple peers and dynamic eBGP/iBGP announcement?
Thanks.
Dmitry
Hi Mate,
Yep on and off for about 15 years, very solid, very reliable. I tend to use Bird this hmorning we rays for this task but Zebra and Quagga are rock solid.
Kindest Regards,
Nathan Brookfield (VK2NAB)
Simtronic Technologies Pty Ltd
Hi Mate,
Yep on and off for about 15 years, very solid, very reliable. I tend to use Bird this hmorning we rays for this task but Zebra and Quagga are rock solid.
Kindest Regards,
Nathan Brookfield (VK2NAB)
Simtronic Technologies Pty Ltd
Hello,
Anybody working with Quagga for production peering with multiple peers and dynamic eBGP/iBGP announcement?
Free Range Routing (FRR) forked Quagga a few years back. I would say it is the new Quagga.
But either flavour handles multiple peers and full routing tables / DFZ with aplomb.
VYOS was Quagga, but now incorporates FRR, and is a good routing workhorse.
Raymond Burkholder wrote:
Anybody working with Quagga for production peering with multiple peers
and dynamic eBGP/iBGP announcement?Free Range Routing (FRR) forked Quagga a few years back. I would say it
is the new Quagga.But either flavour handles multiple peers and full routing tables / DFZ
with aplomb.VYOS was Quagga, but now incorporates FRR, and is a good routing workhorse.
PfSense, too.
<= Used by players as the bgp speaker on edge network nodes. Article is
of the 'famous' experiment from last year. Were use of an experimental
BGP code. Caused FRR bgp speakers to crash. The code error was since be
corrected as an emergency hot-fix.
Quagga is built into one of our core products, works great. That particular vendor a sponsor of frr, and is replacing quagga with frr soon.
Maybe look at the vendor/partner list for quagga and frr, and decide which project has better long-term prospects.
David
Dmitry Sherman <dmitry@interhost.net> writes:
Hello,
Anybody working with Quagga for production peering with multiple peers
and dynamic eBGP/iBGP announcement?
https://frrouting.org/ is a quagga fork and most (all) developers of
quagga mode to frr.
Jens, using frr for quite some time now without any problems
I’ve been meaning to test FRR for a year or so now, so I can get proper native IS-IS support. At the moment, I run Quagga with OSPF and export that into my IS-IS core to drive Anycast services. Anyone on FRR happy with dual-stack IS-IS there, talking to Cisco and Juniper implementations? Mark.
IS-IS, per chance?
Mark.
Mark Tinka <mark.tinka@seacom.mu> writes:
I used to use ISIS for this, but more recently moved to ebgp with 1s/3s timers. The convergence characteristics are reasonable and as the only routing protocol dependence is bgp, we can use bird which in turn allow us to automate provisioning via saltstack. Automating quagga and frr is hacky.
Nick
I prefer to have a number of core systems accessible in the IGP, because
BGP can sometimes get hosed for one reason or another.
BGP always needs IGP to work. The reverse is not true, and reduces us to
absolute basics when it hits the fan (which it has, a few times before).
Mark.
Yeah. I was thinking more for the case of customer-facing anycast resolvers, in which case BGP down means that the network is down, and if the network is down it doesn't matter than DNS is also down because their shared fate means that when BGP is back up, DNS will start working again.
Nick
As much as possible, I'll always choose to have the most basic
infrastructure available under abnormal conditions, regardless of the
service.
ME3600X's and ASR920's, for example, will install 0/0 and ::/0 in FIB
last. If your access to the core depends entirely on BGP in such
scenarios, you will be unable to access the it for as much as 10 minutes.
Mark.
As much as possible, I'll always choose to have the most basic
infrastructure available under abnormal conditions, regardless of the
service.
ME3600X's and ASR920's, for example, will install 0/0 and ::/0 in FIB
last. If your access to the core depends entirely on BGP in such
scenarios, you will be unable to access it for as much as 10 minutes.
Mark.