<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">To manage the AS number of each VM use the bgp protocol configuration of bird</div><div dir="ltr"><br></div><div dir="ltr">Mattia</div><div dir="ltr"><br><blockquote type="cite">Il giorno 20 mar 2020, alle ore 08:33, Fabiano D'Agostino <fabiano.dagostino96@gmail.com> ha scritto:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi, <div>thanks everyone, I read the guide, but I didn't find how to put the two VMs in two different ASs.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno ven 20 mar 2020 alle ore 02:43 Robert Blayzor <<a href="mailto:rblayzor.bulk@inoc.net">rblayzor.bulk@inoc.net</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On 3/19/20 7:11 PM, Chriztoffer Hansen wrote:<br>
> EBGP between two bgp speakers (eg. VMs) is rule of thumb done using<br>
> interfaces on each ebgp speaker in a shared L2 domain, with ip addresses<br>
> on each interface in a shared subnet, eg. Ipv4 /30, /31, IPv6 /64, /126,<br>
> /127.<br>
> If both VMs are on the same hypervisor. A virtual L2 network between VM<br>
> interfaces is the easiest option to get going. 😉<br>
> <br>
<br>
There is no same subnet/L2 adjacency requirement for EBGP peering, only<br>
that the two peers are reachable to each other.<br>
<br>
-- <br>
<a href="http://inoc.net" rel="noreferrer" target="_blank">inoc.net</a>!rblayzor<br>
XMPP: <a href="http://rblayzor.AT.inoc.net" rel="noreferrer" target="_blank">rblayzor.AT.inoc.net</a><br>
PGP: <a href="https://pgp.inoc.net/rblayzor/" rel="noreferrer" target="_blank">https://pgp.inoc.net/rblayzor/</a><br>
</blockquote></div>
</div></blockquote></body></html>