Peering

Requirements

A dn42 ASN and a maintainer object with an ssh-ed25519 or ssh-rsa key in its auth: attribute.
WireGuard.
If you change the auth: keys on your maintainer, or the mnt-by: of your ASN, the change takes effect here 24 hours after it appears in the registry. This guards against a tampered registry mirror.
MP-BGP with extended next hop. One session over IPv6 link-local carries both IPv4 and IPv6 routes.
Valid ROAs for what you announce. Invalid and unknown routes are dropped.

Create a session

ssh -p 4242 <mntner>@dn42.4v1.in

Then run peer_create and answer the prompts:

your ASN
your WireGuard public key
your WireGuard endpoint (an IP address or a hostname) and port
optionally, your own link-local address; leave it empty to use one we generate

peer_config shows both sides of the session: our endpoint, port, public key and link-local address, plus example WireGuard and BIRD configuration for your side. Tunnels are built every five minutes.

Other commands: peer_list, peer_remove (type YES to confirm), help.

Our side


Endpoint	`dn42.4v1.in`, port `23000 + session id` (shown by `peer_config`)
Link-local	`fe80:2174::1:<id>`, or `fe80::2174` if you supply your own address
MTU	1420
Import limit	9000 routes per family

Host key

Check the SSH host key on first connection:

dn42.4v1.in:4242  RSA 3072  SHA256:mKErjDhWJbq3wdPToYpCS5ZICQrsWQZy3uaMIhTr5qA

Software

The SSH service is dn42-sshd-autopeer (MIT) by FLIPFLAP (AS4242420263).

Contact

See Contact.