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

collector updates
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Simon Marsh 2021-04-10 15:58:39 +01:00
parent 239e3bbdd7
commit 0b97f06afe
Signed by: burble
GPG Key ID: 0FCCD13AE1CF7ED8
2 changed files with 35 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
site/content/additional/maintlog/_index.md
View File

@ -7,6 +7,22 @@ A log of changes to the burble.dn42 network.
---
## 10th April 2021
The b.recursive-servers.dn42 DNS resovler is running an experimental build
of pdns-recursor to test a fix of [this issue](https://github.com/PowerDNS/pdns/issues/10263).
Please let me know if you spot any strange problems.
burble.dn42 websites are now using a TLS certificate issued by the
[DN42 ACME](https://acme.dn42) service.
A number of significant changes have been implemented for the global route collector
- Downstream peerings have been stopped, in favour of parsing the MRT dumps
- The collector has moved from de-fra1 to fr-rbx1, where bandwidth is no issue
- A special routing policy has been implemented for the collector to encourage traffic
to go directly to fr-rbx1 and not transit through burble.dn42 nodes. See also the [Routing Policy](/network/routing-policy/#collectordn42) page.
- Internal rate limits on BGP sessions have been relaxed
## 3rd April 2021
The collector is now using a TLS certificate issued by the

19
site/content/network/routing-policy.md
View File

@ -48,5 +48,24 @@ med = (latency between nodes in ms * 10) + (500 per hop)
The med metric is exported to external peers to help them decide how to route traffic to the burble.dn42
network.
## collector.dn42
The global route collector is treated as a special case and does not follow the normal routing policy.
The objective of the collector policy is to steer traffic directly to fr-rbx1 and reduce transit of GRC
traffic over the burble.dn42 network. This is aggressively implemented for certain low bandwidth nodes
to prevent any GRC traffic going through these nodes.
To accomplish this, each node announces the GRC prefix in to DN42 with different levels of path prepending
depending on the available bandwidth of that node. Some nodes with low bandwidth allocations do not
announce the GRC prefix at all.
| Node capability | Action Taken |
|:---|:---|
| fr-rbx1 | Prefix announced without any prepending |
| Other nodes with unlimited BW allowance | ASN prepended once |
| Nodes with BW limits | ASN prepended twice |
| Nodes with low BW limits | GRC prefix not announced |
As well as the external traffic engineering, the internal mesh policy also prevents transit of GRC
traffic via low bandwidth nodes.