BGP in a containers

Thu Jun 14 19:23:55 UTC 2018

re: Exa:

Our use case was both on exporting service IPs as well as receiving routes 
from ToRs.  Exa is more geared towards the former than the latter.  Rather 
then working on getting imports and route installation through Exa, we 
found it simpler with BIRD exporting the service IP from it bound to a 
loopback to run local healthchecks on the nodes and then have them yank the 
service IP from the loopback on failing healthchecks in order to stop 
exporting.

But, YMMV etc.

-- 
Hugo Slabbert       | email, xmpp/jabber: hugo at slabnet.com
pgp key: B178313E   | also on Signal

On Thu 2018-Jun-14 15:07:35 -0400, james jones <james.voip at gmail.com> wrote:

>Yes, that's it.
>
>On Thu, Jun 14, 2018 at 3:05 PM Michel 'ic' Luczak <lists at benappy.com>
>wrote:
>
>>
>> > On 14 Jun 2018, at 20:56, james jones <james.voip at gmail.com> wrote:
>> >
>> > I am working on an personal experiment and was wondering what is the best
>> > option for running BGP in a docker base container. I have seen a lot
>> blogs
>> > and docs referencing Quagga. I just want to make sure I am not over
>> looking
>> > any other options before I dive in. Any thoughts or suggestions?
>>
>> I guess / hope what you’re trying to achieve is to announce services from
>> the containers using BGP. If this is the case, what you’re looking for is
>> called exabgp.
>>
>> ic
>>
>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20180614/4d2a8e04/attachment.sig>