Welcome to the HEADSCARF175 DN42 network — anycast across four POPs in Brisbane (AU), Los Angeles (US), Frankfurt (DE), and Tokyo (JP).
| ASN | AS4242420842 |
| IPv4 Prefix | 172.20.159.128/27 |
| IPv6 Prefix | fdfd:27b9:f174::/48 |
| Domain | headscarf175.dn42 |
| Contact | [email protected] |
| BGP Software | BIRD 2.18.1 (s1, s3) / BIRD 3.2.1 (s2, s4) (per-node) |
| MP-BGP / ENH | Supported (RFC 4760, RFC 8950) |
| RPKI | Validated locally on every POP; ROA-invalid routes rejected |
| Anycast IPv4 | 172.20.159.128 (s1, s2, s3 only — s4 is v6-only origin) |
| Anycast IPv6 | fdfd:27b9:f174::1 |
| Link-Local (peers) | fe80::842/64 |
| MTU | 1420 |
| s1 | Brisbane, AU | s1.headscarf175.net | manual peering only |
| s2 | Los Angeles, US | s2.headscarf175.net | autopeer + manual |
| s3 | Frankfurt, DE | s3.headscarf175.net | autopeer + manual |
| s4 | Tokyo, JP | s4.headscarf175.net | autopeer + manual; v6-only origin (RFC 8950 ENH carries v4 NLRI for transit) |
Per-node WireGuard public keys, tunnel addresses, and assigned ports are returned by autopeer's peer_config command. For s1 (manual only), they are sent in the peering email reply.
WireGuard only. SSH to any cloud node on port 4242 with your DN42 mntner SSH key:
ssh -p 4242 <mntner-lc-no-mnt>@s2.headscarf175.net # Los Angeles ssh -p 4242 <mntner-lc-no-mnt>@s3.headscarf175.net # Frankfurt ssh -p 4242 <mntner-lc-no-mnt>@s4.headscarf175.net # Tokyo
Username is your mntner handle in lowercase with the -MNT suffix removed. Authentication uses the SSH keys attached to your mntner object in the DN42 registry (local mirror syncs ~hourly).
Available shell commands: peer_create, peer_list, peer_config, peer_status, peer_remove, help. Run peer_config after peer_create to retrieve our endpoint, public key, and tunnel addresses.
Ports: autopeer-managed tunnels use UDP 30001-39999 (30000 + row-id). The exact port is returned by peer_config.
s1 (Brisbane) is manual-peering only — residential link, no autopeer. WireGuard, OpenVPN, and GRE/Plain are all accepted.
OpenVPN and GRE/Plain are email-only on every node — autopeer manages WireGuard tunnels only.
GRE/Plain is available on any POP (s1/s2/s3/s4) for peers who require it. No encryption — community (64511, 31) is set on routes via that session instead of (64511, 34) for WG. GRE/IPsec is not supported (esp4/esp6 modules blocked as part of the CVE-2026-43284 mitigation).
Ports: s1 uses sequential UDP 200xx (we'll assign the next free one). s2, s3, and s4 manual peers use last 5 digits of your ASN (e.g. AS4242422189 → UDP 22189).
Send the following template to [email protected]:
I would like to peer with AS4242420842. ASN: Preferred POP (s1/s2/s3/s4/multi): Transport (WireGuard, OpenVPN, or GRE/Plain): WireGuard Endpoint: (if WG) WireGuard Public Key: (if WG) OpenVPN Endpoint + config: (if OpenVPN) GRE Public IP: (if GRE/Plain) -- protocol 47, no port Tunnel IPv6 Link-Local: (preferred for BGP session) Tunnel IPv4 Address: (if using IPv4 BGP)
/27 and /48 as anycast plus their own /29 + /58 for direct steering. s4 announces only the /48 + its /58 (v6-only origin) — v4 NLRI from s4 is exchanged via RFC 8950 ENH on iBGP for transit purposes. See /details.html/27 → 29, /48 → 58(64511, 1..9) | latency tier (set per-peer from measured RTT) |
(64511, 21..29) | bandwidth tier (we set 23, <100Mbps) |
(64511, 31..34) | encryption tier (34 = WireGuard / PFS, 31 = no encryption / GRE) |
(64511, 41..53) | region (per-POP: s1 53 Pacific, s2 44 NAM-W, s3 41 EU, s4 48 East-Asia) |
(64511, 10NN) | ISO-3166-1 country (per-POP: 1036 AU, 1840 US, 1276 DE, 1392 JP) |
We also stamp our own informational large communities at ingress (in our import filters); they pass through unchanged on re-export, so peers and looking glasses see them:
(4242420842, 1, <peer-ASN>) | learned via eBGP from this peer — value is the immediate eBGP neighbour’s ASN |
(4242420842, 120, N) | POP this route entered our network at — 1 s1 (Brisbane), 2 s2 (Los Angeles), 3 s3 (Frankfurt), 4 s4 (Tokyo) |
(4242420842, 130, 1) | learned directly from the origin AS (1-hop AS path at ingress) |
(4242420842, 140, R) | DN42 region we learned it in — same region codes as (64511, 41..53) above |
We have a DN42 phone number via the e164.dn42 ENUM project — 424-0-0842 (i.e. 42400842: the 424-0- prefix plus the last four digits of our ASN).
| Number | 42400842 (+424-0-0842) |
| ENUM domain | 2.4.8.0.0.4.2.4.e164.dn42 |
| NAPTR → | sip:[email protected] |
| SIP / PBX | Asterisk 18 (chan_pjsip) on s1 — codecs opus / g722 / ulaw, UDP 5060 |
Any PBX doing ENUM lookups against e164.dn42 can dial 42400842, or call sip:[email protected] directly. Quick check: dig 2.4.8.0.0.4.2.4.e164.dn42 NAPTR.
No one’s home — the number answers with a short recorded greeting and hangs up.
whois -h whois.headscarf175.dn42 AS4242420842 — serves our local clone of the DN42 registry (refreshed hourly). whois42d, anycast-binding s1's carve-out.