For consistency, I prefer multiprotocol BGP sessions over IPv6. For WireGuard + BIRD users, I recommend using link-local IPv6 addresses. For others, prefer ULA IPv6 addresses to work around various compatibility issues.
If you have multiple nodes, especially in multiple continents, please set up one peering per region to avoid traffic making unnecessary detours.
Note: configuration for this network is stored in a public Git repository. If you would like to keep your endpoint info private, please let me know when submitting your peering request, or simply leave it empty (disables outgoing connections from my end).
OpenVPN peers should send me their keys via Matrix E2EE, PGP-encrypted mail (D5D568B2D34AB32A337944D22EC3F60DE71C0B9D), or some other secure medium.
Extended next hops (IPv4 over IPv6) are supported but not enabled by default.
- Matrix: @james:overdrivenetworks.com
- Email: email@example.com
- Telegram: @jlu5ca
- IRC: jlu5 @ hackint, libera
See the Nodes page for peering details on each server (WireGuard key, IPs, etc.)
peerconfgen - Submissions via Git
The configuration for AS4242421080 is stored in a Git repository. As such, it's possible (but not necessary) to send peering requests and updates directly via GitHub pull requests.
To manage WireGuard peerings, please use the peerconfgen script: this will automatically scrape peering info from any text you paste in, and template BIRD and WireGuard configurations accordingly.
Pull requests are still reviewed manually before deployment - this is not a fully self-service process.