Peering
NATLAN peers on DN42 over WireGuard and BGP. If you run a network there, we would be glad to connect, at whichever site is closest to you.
Before you ask
- 01 A registered ASN and prefixes. Your aut-num, route and route6 objects should be in the DN42 registry before anything comes up; tunnel addresses are checked against them.
- 02 WireGuard. One tunnel per site you peer at.
- 03 MP-BGP with extended next hop, if you can. One session carrying both families, over link-local or a ULA address. Separate IPv4 and IPv6 sessions work too.
- 04 Routes that pass ROA validation. We reject what fails it (not-found is accepted) and cap every session at 8,500 imported prefixes. Please filter what you take from us the same way.
- 05 A way to reach you. So either of us can say when something breaks.
COMMUNITIES
We use the DN42 BGP community scheme, (64511, n). Each site sits in a DN42 origin
region (64511, 41–57), listed below; routes learned on a session can carry the
latency community.
Our side
WireGuard port: assigned per session · 6 of 8 sites up| SITE | ENDPOINT | PUBLIC KEY | LINK-LOCAL | REGION | SESSIONS |
|---|---|---|---|---|---|
| Frankfurt FRA | per session | per session | fe80::28 | 41 | 4 sessions · down |
| Xi'an XIY | per session | per session | fe80::28 | 52 | 0 sessions |
| Guangzhou CAN | can02.peer.dn42.ngworks.cn | per session | fe80::28 | 52 | 3 sessions |
| Shanghai SHA | pvg02.peer.dn42.ngworks.cn | per session | fe80::28 | 52 | 7 sessions |
| Hong Kong HKG | hkg1.edge.ngworks.org | per session | fe80::28 | 52 | 21 sessions |
| Taipei TPE | tpe1.edge.ngworks.org | per session | fe80::28 | 52 | 3 sessions · down |
| Tokyo TYO | tyo1.edge.ngworks.org | per session | fe80::28 | 52 | 8 sessions |
| San Jose SJC | sjc1.edge.ngworks.org | per session | fe80::28 | 44 | 7 sessions |
How it goes
- 01 Send your details Use the form below to put together a request and send it to us.
- 02 We set up our side Tunnel and session at the site you chose; we reply with our endpoint and key, or anything still missing.
- 03 Bring it up Start your side and check the session from the looking glass.
- 04 You count on the map The session count at that site on the atlas goes up by one, and your ASN joins the peers listed there.
Your details
Rather do it by hand, or need something auto-peering does not cover? Fill these in and we will turn them into a request you can copy and send. Nothing is submitted from this page.
DN42 ASNs run AS4242420000–AS4242429999 or AS4201270000–AS4201279999.
YOUR REQUEST
Peering request for NATLAN (AS4242420028) ASN: [your ASN] Contact: [contact] Site: HKG (Hong Kong) Session: Link-local + MP-BGP, extended next hop Endpoint: [host:port] Public key: [WireGuard public key] Link-local: [fe80::xxxx] Our side: fe80::28 at hkg1.edge.ngworks.org
Send it to it@ngworks.cn — or skip the mail and set it up yourself.