DN42 Network
dn42 is a big dynamic VPN, which employs Internet technologies (BGP, whois database, DNS, etc).
I am AS4242420893 on the dn42 network, operating two prefixes as MAIYUN-DN42:172.23.6.160/27fdc0:d227:306::/48
Currently, there are four permanent nodes open for peering:
| Location | AS | Clearnet FQDN |
|---|---|---|
| California 1 | AS7377 | N/A [node name is ab06] |
| California 2 | AS7377 | uc01.dn42.maiyun.me |
| Toronto 1 | AS31898 | ca04.dn42.maiyun.me |
| Chiba 1 | AS31898 | jp02.dn42.maiyun.me |
Looking glass at lg.maiyun.dn42 is only available if you are already inside the dn42 network.
Internal connections are tunnelled via ZeroTier. Internal routing uses Babel and iBGP with a custom-built version of Bird. It propagates routes to other experimental networks like the AMPR 44Net and the AREDN (not exported to dn42).
Peering
Please contact me at dn42admin at maiyun.me with your details. Everything is casual, and there are no clear-cut peering requirements. I prefer using WireGuard and speaking BGP with multiprotocol and extended next hop support.
Node WG Keys can be obtained by querying DNS TXT records on the clearnet FQDN listed above.
If you prefer, a GitHub PR-style semi-AutoPeer is available at myzhang1029/dn42-config-pub. Kindly fork and clone the repo and run ./make_peering.py.
My internal network is capable of routing AMPR 44Net traffic as well. I'll be happy to exchange those prefixes if you can show proof of allocation. I am also interested in trying dn42 peering over 44Net IPs (although double/triple tunnelling is likely detrimental to performance).