You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With BGP Unnumbered (RFC 5549) , peering sessions do not require a local or remote address.
Instead, BGP Unnumbered sessions are bound to an interface (point-to-point links).
This is commonly used when EVPN is deployed in a datacenter.
Hi @jlanclos! All data models should represent real world objects, bgp session in real world always has ip source and destination address. BGP Unnumbered is just a syntactic sugar in configuration. Device gets source and destination addresses from /31 or /32 prefix setted on the interface. What i can do with this plugin is make this "syntactic sugar" inside the plugin which will choise source and destionation addresses from interface prefix. But in that way you have to bind address to interface before create session.
From playing with it, yes, you have to track the link-local to use this plugin if you doing truly unnumbered which means use dynamically assigned. We also assign an loopback address for VXLAN tunnels, so it appears that would have to be used to create all the unnumbered sessions. which grows quickly in an EVPN/VXLAN network..
With BGP Unnumbered (RFC 5549) , peering sessions do not require a local or remote address.
Instead, BGP Unnumbered sessions are bound to an interface (point-to-point links).
This is commonly used when EVPN is deployed in a datacenter.
Here is an example of underlay config in frr:
To accommodate BGP Unnumbered, add a Type selection to the Session: ['IPv4','Interface']
When "Interface" is selected:
The text was updated successfully, but these errors were encountered: