From 07484efbab2b2d2f24e0eee0839c4f826c695141 Mon Sep 17 00:00:00 2001 From: Simon Marsh Date: Mon, 17 Jun 2019 10:01:29 +0100 Subject: [PATCH] Add note about multiple peerings --- pages/02.peering/default.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/pages/02.peering/default.md b/pages/02.peering/default.md index 47a7bcf..bbaa24e 100755 --- a/pages/02.peering/default.md +++ b/pages/02.peering/default.md @@ -111,8 +111,8 @@ The burble.dn42 network uses [bird 2](https://bird.network.cz/?get_doc&f=bird.ht * Multiprotocol BGP [RFC 4760](https://www.rfc-editor.org/info/rfc4760) * BGP Large Communities [RFC 8092](http://www.rfc-editor.org/info/rfc8092) * BGP Confederations [RFC 5065](https://www.rfc-editor.org/info/rfc5065) -* dn42 Route Origin Authorisation (ROA - see below section on Route Filtering) -* dn42 [BGP communities](https://wiki.dn42.us/howto/Bird-communities) +* DN42 Route Origin Authorisation (ROA - see below section on Route Filtering) +* DN42 [BGP communities](https://wiki.dn42.us/howto/Bird-communities) * burble.dn42 custom [large communities](/home/bgp-communities) * burble.dn42 [Routing Policy](/home/routing-policy) @@ -146,6 +146,16 @@ IPv6 fd00::/8{44,64} ``` +**Peering with Multiple Nodes** + +Users are welcome to peer with more than one node in the burble.dn42 network. + +Note that the regional routing policy means that peering with multiple nodes within the same +DN42 region will help provide resiliency, but is unlikely to provide additional route paths. +Peering with nodes in different regions and implementing the DN42 +[BGP communities](https://wiki.dn42.us/howto/Bird-communities) will help provide more optimal +and varied routes. + #### Testing Within the tunnel, hosts respond to ping and traceroute, but also have the echo (port 7) and daytime (port 13) services enabled. These can be used to check the tunnel is up and configured correctly. @@ -173,7 +183,7 @@ Once peering is established I have a BGP looking glass [here](https://lg.burble. The burble.dn42 is fully meshed between nodes using wireguard tunnels and VXLAN. However, the network is configured as a number of sub-AS regions within a single BGP confederation to allow for regional services and to reduce the number of iBGP sessions. See the [about](/about) page for more details and a network diagram. The internal, confederation ASNs documented here are *for information only* as they are not valid DN42 ASNs. -When peering with burble.dn42 the DN42 assigned AS4242422601 should always be used. +When peering with burble.dn42 the DN42 assigned AS4242422601 should always be used. ||| |---|---|