On 18/Mar/20 22:22, Nick Hilliard wrote:
> 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
On 18/Mar/20 22:22, Nick Hilliard wrote:
>
> 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 BG
Mark Tinka wrote on 18/03/2020 17:02:
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
On 18/Mar/20 18:01, Nick Hilliard wrote:
>
> 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
Mark Tinka wrote on 18/03/2020 14:25:
At the moment, I run Quagga with OSPF and export that into my IS-IS core
to drive Anycast services.
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 pro
Mark Tinka writes:
> On 17/Mar/20 19:39, Jens Link wrote:
>
>>
>> Jens, using frr for quite some time now without any problems
>
> IS-IS, per chance?
Sorry, only BGP for now.
Jens
--
| Delbrueckstr. 41| 12051 Berl
On 17/Mar/20 19:39, Jens Link wrote:
>
> Jens, using frr for quite some time now without any problems
IS-IS, per chance?
Mark.
On 17/Mar/20 19:18, Hiers, David wrote:
>
> 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 lon
Dmitry Sherman 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
-boun...@nanog.org] On Behalf Of Nathan Brookfield
Sent: Sunday, February 23, 2020 4:41 AM
To: Dmitry Sherman
Cc: nanog@nanog.org
Subject: Re: Quagga for production?
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
Raymond Burkholder wrote:
> On 2020-02-23 5:26 a.m., Dmitry Sherman 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
>
On 2020-02-23 5:26 a.m., Dmitry Sherman wrote:
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
:
Hello,
Anybody working with Quagga for production peering with multiple peers and
dynamic eBGP/iBGP announcement?
Thanks.
Dmitry
:
Hello,
Anybody working with Quagga for production peering with multiple peers and
dynamic eBGP/iBGP announcement?
Thanks.
Dmitry
Hello,
Anybody working with Quagga for production peering with multiple peers and
dynamic eBGP/iBGP announcement?
Thanks.
Dmitry
15 matches
Mail list logo
