We peer over WireGuard and BGP (BIRD) within the DN42 network. This page and our peering policy are a work in progress and will be expanded over time.
✦ Quick start — default setup
If you are fine with our defaults (BGP-MP with BGP-Extended-Next-Hop over link-local addresses), all we need from you is:
- Your ASN
- Your endpoint (
host:port) - Your WireGuard public key
- Optional: a WireGuard preshared key
- Your link-local address
Contact
- Email: allen [at] moe [dot] cat
- Telegram: @Astro + Profundis
General policy
- We prefer multi-protocol BGP peers (IPv4 + IPv6)
- Peers must maintain valid ROAs covering their announced prefixes
- A peer’s POP should have less than 20ms latency to at least one of our POPs
- Peering requests should include the information listed below
- Peers down for more than 30 days may be removed without notice
Required information
When requesting peering, please provide:
- Your DN42 ASN
- DN42 IPv4 and IPv6 addresses, or a link-local IPv6 address if you use BGP-MP with BGP-Extended-Next-Hop
- WireGuard public key
- Preferred Hoshi node (see the open-for-peering list)
- Your endpoint (host and port)
- Contact details
- Any other relevant details, e.g. tunnel MTU
We prefer establishing BGP neighbors over WireGuard using BGP-MP with BGP-Extended-Next-Hop. If you need a different setup, please let us know.
Our default WireGuard MTU is 1408. WireGuard data packets may be padded to a 16-byte boundary, so we choose a 16-aligned value to reduce surprises when peers or outer paths have different MTU limits. This is a compatibility choice, not a protocol requirement; if your side keeps the common WireGuard MTU of 1420, it usually works as long as the actual path MTU can carry it.
Unless otherwise agreed, our WireGuard endpoint port is derived from your ASN as follows:
- ASN 424242xxxx → last 5 digits (2xxxx)
- ASN 420127xxxx → 3 + last 4 digits (3xxxx)
- ASN 6xxxx → 4 + last 4 digits (4xxxx)
- Other ASN ranges → 1 + last 4 digits (1xxxx)