burble.dn42/www
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity

Add note about multiple peerings

Browse Source
This commit is contained in:
Simon Marsh 2019-06-17 10:01:29 +01:00
parent 9d8da7dfba
commit 07484efbab
Signed by: burble
GPG Key ID: 7B9FE8780CFB6593
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pages/02.peering/default.md
View File

@ -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.
|||
|---|---|