☰

Updated Bird2.md (markdown)

burble.dn42 wiki mirror (uk-lon1) committed 2024-08-08 09:50:25 +0000 commit 708c5397ffe6bcc5e4e69b271e3dd4e7498c37d6

				howto/Bird2.md
			
          @@ -205,6 +205,10 @@ protocol bgp <NEIGHBOR_NAME>_v6 from dnpeers {

           Due to the special link local addresses of IPv6, an interface has to be specified using the `%<if>` or the `interface <if>;` syntax if a link local address is used (Which is recommended)

          +## Note on multiprotocol BGP and extended next hops

          +This configuration example shows the required configuration without using multiprotocol BGP and extended next hops.

          +These two options are helpful if one desires to optimize their peering by reducing the session count per peer to 1 (in the case of multiprotocol BGP) and remove the need to have IPv4 tunnel IP addresses (in the case of Extended next hops over IPv6)

          +

           # BGP communities

           Communities can be used to prioritize traffic based on different flags, in DN42 we are using communities to prioritize based on latency, bandwidth and encryption. It is really easy to get started with communities and we encourage all of you to get the basic configuration done and to mark your peerings with the correct flags for improved routing.

...	...	@@ -205,6 +205,10 @@ protocol bgp <NEIGHBOR_NAME>_v6 from dnpeers {
205	205
206	206	Due to the special link local addresses of IPv6, an interface has to be specified using the `%<if>` or the `interface <if>;` syntax if a link local address is used (Which is recommended)
207	207
	208	+## Note on multiprotocol BGP and extended next hops
	209	+This configuration example shows the required configuration without using multiprotocol BGP and extended next hops.
	210	+These two options are helpful if one desires to optimize their peering by reducing the session count per peer to 1 (in the case of multiprotocol BGP) and remove the need to have IPv4 tunnel IP addresses (in the case of Extended next hops over IPv6)
	211	+
208	212	# BGP communities
209	213
210	214	Communities can be used to prioritize traffic based on different flags, in DN42 we are using communities to prioritize based on latency, bandwidth and encryption. It is really easy to get started with communities and we encourage all of you to get the basic configuration done and to mark your peerings with the correct flags for improved routing.