AS4242420842 - HEADSCARF175

Welcome to the HEADSCARF175 DN42 network — anycast across seven POPs in Brisbane (AU), Los Angeles (US), New Jersey (US), Frankfurt (DE), Tokyo (JP), Hong Kong, and Singapore.

Network Information

POPs

Nodes were renamed from s1/s2/s3/s4 to geo names in July 2026; the former s1.headscarf175.net .. s4.headscarf175.net endpoints remain valid permanently (CNAME to the new names), so existing tunnels need no change.

Per-node WireGuard public keys, tunnel addresses, and assigned ports are shown by the peering portal (below). For au-bne01 (manual only), they are sent in the peering email reply.

Auto-peering (us-lax01, de-fra01, jp-tyo01, us-ewr01, hk-hkg01, sg-sin01)

WireGuard only, via the self-service web portal:

DN42:      https://peer.headscarf175.dn42
clearnet:  https://peer.headscarf175.net

Sign in with your DN42 mntner (OIDC via iedon's auth42 / oauth.dn42 — password, email, PGP, or SSH). Create and remove sessions at any cloud POP; the portal shows our endpoint, public key, tunnel addressing, a ready-to-use WireGuard config for your side, and live session status.

Ports: portal-managed tunnels use UDP 30001-39999; your exact port is shown on the session page. (The legacy SSH autopeer on port 4242 is retired — existing sessions were migrated unchanged.)

Direct IX peering

Members of Yukisino IX and SVIX can establish a direct bilateral BGP session with us across the shared IX fabric, without a WireGuard tunnel.

MP-BGP over IPv6 with RFC 8950 Extended Next Hop is supported. Email [email protected] with your ASN, IX name, and on-fabric BGP address to request a session.

Manual peering (au-bne01, OpenVPN, GRE/Plain)

au-bne01 (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 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: au-bne01 uses sequential UDP 200xx (we'll assign the next free one). us-lax01, de-fra01, jp-tyo01, us-ewr01, hk-hkg01, and sg-sin01 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 (au-bne01/us-lax01/de-fra01/jp-tyo01/us-ewr01/hk-hkg01/sg-sin01/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)

Peering Policy

• Open peering — anyone registered in DN42 is welcome
• No tunnel endpoints in mainland China — PRC cross-border-tunnel licensing means we can't terminate a session at an endpoint that geolocates to mainland CN. The restriction is mainland CN only: Hong Kong, Macau, and Taiwan endpoints are all fine, as are offshore (non-CN) POPs of operators registered in CN — just point the tunnel at your non-CN node. The Hong Kong POP enforces this automatically.
• WireGuard preferred (and required for autopeer); OpenVPN and GRE/Plain accepted via email only
• MP-BGP over IPv6 link-local preferred
• Geographic best-fit: AU/Pacific peers on au-bne01 · West-coast/Latin-American peers on us-lax01 · US-East/Canadian peers on us-ewr01 · European peers on de-fra01 · JP/Korea peers on jp-tyo01 · HK/Taiwan/South-China peers on hk-hkg01 · SG/SE-Asia peers on sg-sin01. Multi-homed peers across two or more POPs are welcome and routed via per-POP MED.

BGP

• iBGP full-mesh between au-bne01, us-lax01, de-fra01, jp-tyo01, us-ewr01, hk-hkg01, sg-sin01 (next-hop-self)
• Core POPs announce the IPv4 /27 and IPv6 /48 anycast aggregates. Per-node IPv6 /58s are advertised externally with home-aware steering; per-node IPv4 /32s stay inside our iBGP/Babel underlay and are never advertised externally. jp-tyo01 has no per-node v4 origin, but carries v4 NLRI via RFC 8950 ENH for transit. See /details.html
• RPKI/ROA validated locally on every POP; invalids dropped
• Registry max-lengths: /27 → 27, /48 → 58
• Supported RFCs: 1997, 4724, 4760, 6811, 7311, 7313, 7911, 7947, 7999, 8092, 8326, 8654, 8950, 9003, 9072, 9494, 9687

Communities tagged on announce

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:

Telephony (tel.dn42)

We have a DN42 phone number via the registry-managed tel.dn42 ENUM project — +04240842 (formatted +042-4-0842: the +042- prefix, the 424242xxxx block digit, plus the last four digits of our ASN).

Any PBX doing ENUM lookups against tel.dn42 can dial 04240842, or call sip:[email protected] directly. Quick check: dig 2.4.8.0.4.2.4.0.tel.dn42 NAPTR.

No one’s home — the number answers with a short recorded greeting and hangs up.

Resources

• GeoFeed
• Flap dashboard — live BGP route-flap monitor (FlapAlerted)
• Whois: whois -h whois.headscarf175.dn42 AS4242420842 — serves our local clone of the DN42 registry (refreshed hourly). whois42d, served from au-bne01 + de-fra01.
• Network details — per-POP carve-outs, nameservers