diff --git a/pages/01.home/maintenance-log/default.md b/pages/01.home/maintenance-log/default.md index cb4ed20..b292cb4 100755 --- a/pages/01.home/maintenance-log/default.md +++ b/pages/01.home/maintenance-log/default.md @@ -10,6 +10,15 @@ A log of changes to the burble.dn42 network. ## burble.dn42 Maintenance Log +#### 16th May 2020 + +Approximately 40 old or inactive peers have been deleted as part of a spring cleaning +exercise. + +If you've been accidently deleted and still want to peer with me, just give me a shout +and I will re-instate the configuration. + + #### 11th May 2020 Rate limiting on BGP sessions has been implemented to protect the network from major diff --git a/pages/02.peering/default.md b/pages/02.peering/default.md index 3f106b6..9024f98 100755 --- a/pages/02.peering/default.md +++ b/pages/02.peering/default.md @@ -7,15 +7,36 @@ Peering with burble.dn42 This page provides the information to get started on peering with the burble.dn42 network. burble.dn42 is a set of global POPs integrated to the [dn42](https://dn42.us/) network, and -new peering requests are welcome, whether you are a new starter or already have an established -network. A description of the network is available in the [about](/about) page. +new peering requests are welcome. A description of the network is available in the +[about](/about) page. + +burble.dn42 is a large network and there are some restrictions in place to protect both +this network and the rest of the DN42 network. +Please ensure you read the information below before requesting to peer. ####Peering Requests Please mail **dn42@burble.com** if you'd like to peer with me. -By default, I'll configure a full transit connection with you which could mean I end up routing -traffic over your network, but just let me know if you'd prefer a different peering arrangment. +**Peering Requirements** + +To peer with burble.dn42, you must meet the following requirements: + +* You must have at least **two** peerings already established with other DN42 networks + + *Sorry, but burble.dn42 is not open to new starters. If you are a new starter in DN42 + please use the [peerfinder](https://dn42.us/peers) or ask on [IRC](https://dn42.dev/services/IRC); + there lots of other networks who will be happy to peer with you, and some even offer automatic + peering. + This is a tough restriction, but one that is in place to promote network diversity.* + +* You must support IPv6 +* You must implement ROA checks + +* Contact information in the registry must always be up to date and admins must repond when contacted + + *Contacts must also be reachable in case of problems. In addition, the network is ever + evolving and failure to respond to change notices may result in your peering being suspended.* At a minimum, I'll need to know the following in order to establish a peering: @@ -28,11 +49,13 @@ At a minimum, I'll need to know the following in order to establish a peering: * Any special config you need that is different to my defaults * IP addresses of your end of the tunnel * Typically these will be a single IPv4/32 and IPv6/128 from your DN42 allocation +

+ +All peerings will be configured as a full transit session. #### Residential ISPs and Dynamic IP addresses -A 24/7 connection, with static IP addresses are the norm for DN42, and by default I will add -firewall rules to limit tunnel traffic to your specific IP address. If you are connecting from a +A 24/7 connection, with static IP addresses are the norm for DN42. If you are connecting from a residential ISP or otherwise have a dynamic IP please let me know so that I can configure my side appropriately. If you don't do tell me, the peering will stop working when your IP address changes. @@ -111,7 +134,8 @@ There are no other controls applied to transit or non-BGP traffic. |**ASN**|AS4242422601|   -The burble.dn42 network uses [bird 2](https://bird.network.cz/?get_doc&f=bird.html&v=20), and the +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) @@ -122,6 +146,9 @@ following features are supported: * burble.dn42 custom [large communities](/home/bgp-communities) * burble.dn42 [Routing Policy](/home/routing-policy) +The source code for the custom bird used on the network is available on +[git.burble.dn42](https://git.burble.dn42/burble.dn42/bird) + **Route Filtering** The network applies strict Route Origin Authorisation (ROA) filtering to all @@ -176,7 +203,7 @@ $ ``` Once peering is established I have a BGP looking glass [here](https://lg.burble.com/) (public -internet link) and global route [collector](https://collector.burble.com) which can be used to +internet link) and global route [collector](https://grc.burble.com) which can be used to check routing. The looking glass is a key resource for you to use when understanding how your routes are propogating around the DN42 network.