diff --git a/site/content/additional/maintlog/_index.md b/site/content/additional/maintlog/_index.md index af00b1f..7545b8d 100644 --- a/site/content/additional/maintlog/_index.md +++ b/site/content/additional/maintlog/_index.md @@ -7,6 +7,20 @@ A log of changes to the burble.dn42 network. --- +## 25th March 2021 + +Bird [2.0.8](https://gitlab.nic.cz/labs/bird/-/blob/master/NEWS) has been deployed +across the network. Please let me know if you see problems. + +burble.dn42 uses a custom bird build that includes additional debugging. The +source code for the build is available on [git.burble.dn42](https://git.burble.dn42). + +{{}} +**Advanced Notice** +- us-nyc1 will be decommissioned before 15/04/21 +- us-chi1 will be decommissioned before 14/05/21 +{{}} + ## 23rd February 2021 Updated IPv6 address for hk-hkg1 diff --git a/site/content/network/peering.md b/site/content/network/peering.md index fe5a621..112905e 100644 --- a/site/content/network/peering.md +++ b/site/content/network/peering.md @@ -47,12 +47,13 @@ At a minimum, I'll need to know the following in order to establish a peering: * The burble.dn42 node you would like to peer with * Your ASN * The public address of your host -* The tunnel parameters, e.g. +* The tunnel and BGP parameters, e.g. * Port number, if using wireguard or OpenVPN * Public key for wireguard * Any special config you need that is different to my defaults + * (see the [Supported Tunnel Types](https://wdev.burble.dn42:443/network/peering/#supported-tunnel-types) and [BGP Feature Support](https://wdev.burble.dn42/network/peering/#bgp-feature-support) sections) * IP addresses of your end of the tunnel - * Typically these will be a single IPv4/32 and IPv6/128 from your DN42 allocation + * Typically these will be a single IPv4/32 and Link-Local IPv6 address

All peerings will be configured as a full transit session. @@ -70,7 +71,9 @@ peering may stop working when your IP address changes. **Peering in Multiple Locations** If you have multiple nodes, you are welcome to peer in several locations -to provide additional redundancy and route choice. +to provide additional redundancy and route choice. Routes exported from the +network include a latency based MED attribute to help peers +optimise their routing (See the [Routing Policy](https://wdev.burble.dn42:443/network/routing-policy/#bgp-med)) It's highly recommended to peer with multiple users DN42 users though, it's lots of fun and you should never rely on just one user for your connectivity. @@ -84,7 +87,7 @@ I also support OpenVPN tunnels. #### Wireguard - The port number will be 2xxxx where xxxx is the last four digits of your ASN. -- Each peer is assigned a unique encryption key, pre-shared keys are also supported. +- Each peer is assigned a unique encryption key, pre-shared keys are also supported (but not enabled by default). - Endpoint names and IP addresses are detailed in the [nodes](/network/nodes) page. My wireguard AllowedIPs are: @@ -120,7 +123,7 @@ auth sha256 ### Allowed Traffic -Only the network ranges will be forwarded through the DN42 network, all other +Only the following network ranges will be forwarded through the DN42 network, all other traffic will be dropped. IPv4 @@ -144,10 +147,10 @@ DN42 network. A typical BGP session in DN42 will use a trivial amount of traffic. However, for large networks like burble.dn42 some transient events, such as BGP flapping, can generate multi MB/sec traffic flows that -damange the network and create instability across DN42. +damage the network and create instability across DN42. -To protect the network from misconfigurations and prevent excessive updates from being propagated to the -rest of DN42, the burble.dn42 network implements rate limiting on direct BGP sessions. The rate limiting +To protect the network from misconfigurations and prevent excessive updates from propagating to the +rest of DN42, the burble.dn42 network implements rate limiting on BGP sessions. The rate limiting activates when a large amount of BGP traffic is seen (typically 10's or 100's of thousands of updates a second) over a sustained period and will typically reset automatically within an hour. @@ -167,9 +170,11 @@ The burble.dn42 network uses a custom build of [bird 2](https://bird.network.cz/?get_doc&f=bird.html&v=20), and the following features are supported: -* 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) +* 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) +* Extended Next Hop - [RFC 5549](https://www.rfc-editor.org/info/rfc5549) +* Extended Messages - [RFC 8654](https://www.rfc-editor.org/info/rfc8654) * 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](/network/communities) @@ -178,6 +183,14 @@ following features are supported: The source code for the custom bird used on the network is available on [git.burble.dn42](https://git.burble.dn42/burble.dn42/bird) +#### Default Extensions + +Multiprotocol BGP is preferred, however it is not enabled by default as not all +peers can support it. Please let me know when peering if you can support a +multiprotocol BGP session. + +Extended next hop and extended message support are both enabled by default. + ### Route Filtering The network applies strict Route Origin Authorisation (ROA) filtering to all @@ -234,7 +247,7 @@ $ Once peering is established I have a [BGP looking glass](https://lg.burble.com/) (public internet link) and global route [collector](https://grc.burble.com) which can be used to check routing configuration. Looking glasses are a key, self-service resource for you -to use when understanding how your routes are propogating around the DN42 network, please +to use when understanding how your routes are propagating around the DN42 network, please take the time to learn how to use them. ### Speed Test