[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bird-users
Subject:    Re: [RFC] Automatic MP peering with IPv6 link local peers
From:       Hugo Slabbert <hugo.slabbert () menlosecurity ! com>
Date:       2022-07-15 15:27:41
Message-ID: CAOx9P4-vTLQWYrFhbLSWrcG--hLAOzicSzjFfm-6pCXhrHO0dg () mail ! gmail ! com
[Download RAW message or body]

We did similar at a previous gig, though the switches did not support BGP
unnumbered so there was an initial DHCP bootstrap to hit a couple of
microservices to retrieve identity info (upsert local server's ASN;
retrieve switch peer ASNs), but then turned up peering and off you go.

But I digress:
It would be fantastic if BIRD could support interface-specified unnumbered
BGP over IPv6 LL with an RA bootstrap and 5549-based 4-over-6.

On Thu, Jul 14, 2022 at 2:42 PM Douglas Fischer <fischerdouglas@gmail.com>
wrote:

> This thread reminded me of something I saw these days about using BGP
> unnumbered in Hypervisors for EVPN/VXLAN.
>
> I confess that I was completely stunned to see how beautiful it was!
>
> - The 4 ports of each Server became a CLOS L3 topology.
> - The complexities of Multichassis-LAG no longer exist.
> - The establishment of neighborhoods was almost automatic.
> - And the ToR switches became only simple L3 routers, without even knowin=
g
> of the existence of Overlay. Which made them much cheaper and simpler to
> operate.
>
> Em qui., 14 de jul. de 2022 =C3=A0s 12:40, Marco d'Itri <md@linux.it> esc=
reveu:
>
>> On Jul 14, Ondrej Zajicek <santiago@crfreenet.org> wrote:
>>
>> > > RFC 8950 is what has been implemented in Cumulus.
>> > Not sure how that is relevant, RFC 8950 is just IPv6 next hop for IPv4
>> > routes, it does not handle BGP neighbor discovery.
>> Discovery is just looking at Router Advertisements for the link, then
>> you need RFC 8950.
>>
>>
>> https://www.theasciiconstruct.com/post/cumulus-basics-part-v-bgp-unnumbe=
red/
>> <https://isolate-menlo.menlosecurity.com/0/eJwNzDkOhDAMAMC_uMZYFDT5TWIii=
EQO-SDFav8O84D5gcsNAS6zoYFozrnalaNyKdybmjjbyr3S6GrEXv12xRS1sOKIYvhgOgd6a15T=
lnwQLCAdwraAleO7tx3-L-LkJKs>
>>
>> https://www.theasciiconstruct.com/post/junos-bgp-and-bgp-unnumbered/#bgp=
-unnumbered-bgp-auto-discovered-neighbors
>> <https://isolate-menlo.menlosecurity.com/0/eJxVjrsOgzAMRf_FXQkRQ5f8DXmIG=
IEdxXYzVP13Kjp1ujpHZ7hvsH5AgKraJHg_xpi1llUSYmIS7ZZ0Tnz6xqJ-N2JxcWtupXyvEdkZ=
Sy_ZP_75l5myyyiJX7ejgluN3AUm6AxhmUAxfw8sT_hciJ4ytg>
>>
>> --
>> ciao,
>> Marco
>>
>
>
> --
> Douglas Fernando Fischer
> Eng=C2=BA de Controle e Automa=C3=A7=C3=A3o
>

[Attachment #3 (text/html)]

<div dir="ltr">We did similar at a previous gig, though the switches did not support \
BGP unnumbered so there was an initial DHCP bootstrap to hit a couple of \
microservices to retrieve identity info (upsert local server&#39;s ASN; retrieve \
switch peer ASNs), but then turned up peering and off you go.<div><br></div><div>But \
I digress:<br>It would  be fantastic  if BIRD could  support interface-specified \
unnumbered BGP over IPv6 LL with an RA bootstrap and 5549-based \
4-over-6.</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Thu, Jul 14, 2022 at 2:42 PM Douglas Fischer &lt;<a \
href="mailto:fischerdouglas@gmail.com">fischerdouglas@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">This \
thread reminded me of something I saw these days about using BGP unnumbered in \
Hypervisors for EVPN/VXLAN.<br><br>I confess that I was completely stunned to see how \
beautiful it was!<br><br>- The 4 ports of each Server became a CLOS L3 topology.<br>- \
The complexities of Multichassis-LAG no longer exist.<br>- The establishment of \
neighborhoods was almost automatic.<br>- And the ToR switches became only simple L3 \
routers, without even knowing of the existence of Overlay. Which made them much \
cheaper and simpler to operate.<br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">Em qui., 14 de jul. de 2022 Ã s 12:40, Marco d&#39;Itri &lt;<a \
href="mailto:md@linux.it" target="_blank">md@linux.it</a>&gt; \
escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Jul 14, Ondrej \
Zajicek &lt;<a href="mailto:santiago@crfreenet.org" \
target="_blank">santiago@crfreenet.org</a>&gt; wrote:<br> <br>
&gt; &gt; RFC 8950 is what has been implemented in Cumulus.<br>
&gt; Not sure how that is relevant, RFC 8950 is just IPv6 next hop for IPv4<br>
&gt; routes, it does not handle BGP neighbor discovery.<br>
Discovery is just looking at Router Advertisements for the link, then <br>
you need RFC 8950.<br>
<br>
<a href="https://www.theasciiconstruct.com/post/cumulus-basics-part-v-bgp-unnumbered/" \
rel="noreferrer" target="_blank">https://www.theasciiconstruct.com/post/cumulus-basics-part-v-bgp-unnumbered/</a><br>
 <a href="https://www.theasciiconstruct.com/post/junos-bgp-and-bgp-unnumbered/#bgp-unnumbered-bgp-auto-discovered-neighbors" \
rel="noreferrer" target="_blank">https://www.theasciiconstruct.com/post/junos-bgp-and-bgp-unnumbered/#bgp-unnumbered-bgp-auto-discovered-neighbors</a><br>
 <br>
-- <br>
ciao,<br>
Marco<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr">Douglas Fernando Fischer<br>Eng º de Controle e Automação<br><div \
style="padding:0px;margin-left:0px;margin-top:0px;overflow:hidden;color:black;text-align:left;line-height:130%;font-family:&quot;courier \
new&quot;,monospace"></div></div></div> </blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic