Skip to main content

Peering

Last updated: 2026-05-21 Contact: Telegram @cloudc001 | Email: cloudc001#outlook.com

Auto Peer#

You can use a Telegram bot to automate peer-related tasks.

您可以通过 TG机器人 自助与我peer

Network Overview#

ItemValue
ASNAS4242423777
Allocated Prefixes172.22.107.0/27, fdbb:aee:d9bd::/48
Peering PolicyOpen — all requests welcome
Tunnel TypeWireGuard only
Internal IGPOSPFv2 / OSPFv3
ArchitectureFull-Mesh + Route Reflector (HK & US as RR)

Peering Policy#

General Rules#

  • WireGuard only — no other tunnel types supported.
  • Multi-Protocol BGP + Extended Next Hop + IPv6 LLA is preferred. Other modes supported for compatibility — please contact me.
  • I may terminate the session if your node is unreachable for an extended period.
  • Please try Telegram first; email replies within 24 hours.

WireGuard Port Assignment#

Your default WireGuard listen port is:

2+Last 4 digits of your ASN is the default WireGuard listen port for you, please let me know if you have speical needs.

e.g. ASN 4242420197 → port 20197. Let me know if you need a different port.

IPv4-Only / IPv6-Only Endpoint#

If you need a single-stack tunnel endpoint, prefix my domain with 4. (IPv4-only) or 6. (IPv6-only):

  • 4.us.cloudc.dev — IPv4-only tunnel to US node
  • 6.sg.cloudc.dev — IPv6-only tunnel to SG node
CN 中国大陆地区须知

CN节点不与非大陆节点Peer，禁止用于违规跨境传输，实时抓包，发现拉黑

Node List#

Please try to keep latency under 50ms if possible.

I am expanding — recommendations for affordable VPS providers are welcome!

HK (WAWO)#

AttributeValue
ASN4242423777
Endpointhk.dn42.cloudc.dev
WireGuard Public KeyZynDjBdOWAS1YjZzwdiSI4kbthisE2xgPiOHopdfIxQ=
Link-Localfe80::3777
DN42 IPv4172.22.107.1
DN42 IPv6fdbb:aee:d9bd::1
Endpoint For V6Supported

JP (Legendvps) - Tokyo#

AttributeValue
ASN4242423777
Endpointjp.dn42.cloudc.dev
WireGuard Public KeyTRsJBPvVUXBCDuiBDwte+YCbkjkIglfVm+M5NxOFfwk=
Link-Localfe80::3777
DN42 IPv4172.22.107.2
DN42 IPv6fdbb:aee:d9bd::2
Endpoint For V6Supported

SG (Legendvps)#

AttributeValue
ASN4242423777
Endpointsg.dn42.cloudc.dev
WireGuard Public KeyEPgqX4UDrzirYgPbDf3t6+6XBWozuUEg4L2zWcPO5Xk=
Link-Localfe80::3777
DN42 IPv4172.22.107.3
DN42 IPv6fdbb:aee:d9bd::3
Endpoint For V6Supported

TH (MetraByte)#

AttributeValue
ASN4242423777
Endpointth.dn42.cloudc.dev
WireGuard Public KeydWOQkOyFT7VeHzh/8DNnlMIwqLPBh0/Daj6MdOdR9BQ=
Link-Localfe80::3777
DN42 IPv4172.22.107.4
DN42 IPv6fdbb:aee:d9bd::4
Endpoint For V6Not Supported

US (GCP) - Council Bluffs#

AttributeValue
ASN4242423777
Endpointus.dn42.cloudc.dev
WireGuard Public KeyH7LRdH2HlvsKM/ftF7CEHIja8AnFV5c5tYJ1OSyrlnQ=
Link-Localfe80::3777
DN42 IPv4172.22.107.5
DN42 IPv6fdbb:aee:d9bd::5
Endpoint For V6Not Supported

UK (WePC) - London#

AttributeValue
ASN4242423777
Endpointuk.dn42.cloudc.dev
WireGuard Public Keyb9BF2pBj3Uk958jzSUIIPzKN2DLpED/JldkSo4S+VAM=
Link-Localfe80::3777
DN42 IPv4172.22.107.6
DN42 IPv6fdbb:aee:d9bd::6
Endpoint For V6Not Supported

DE (C-Servers) - Free State of Saxony#

AttributeValue
ASN4242423777
Endpointde.dn42.cloudc.dev
WireGuard Public KeyyJy4AxORf1c2VNvmVCzM9HYd6+xru17rc/N+946PODQ=
Link-Localfe80::3777
DN42 IPv4172.22.107.7
DN42 IPv6fdbb:aee:d9bd::7
Endpoint For V6Supported

CN#

Contact me directly for node information (Endpoint / Public Key / IPs). CN node does not peer with non-mainland nodes.

BGP & Community Support#

My routers run BIRD and support traffic engineering via BGP Communities.

Standard Communities (RFC 1997)#

CommunityAction
65535:65281 (NO_EXPORT)Do not advertise to eBGP peers
65535:65282 (NO_ADVERTISE)Do not advertise at all (local only)

DN42 Large Communities — Smart Routing Engine#

Routes tagged with the following communities get automatic Local Preference adjustment on my side. Lower latency & higher bandwidth → higher preference.

Latency (64511:1:x):

CommunityLatencyPriority
64511:1:1< 10msHighest
64511:1:2< 50msHigh
64511:1:3< 100msMedium
64511:1:4< 200msLow
64511:1:9> 200msPenalized

Bandwidth (64511:2:x):

CommunityBandwidthPriority
64511:2:21< 1 MbpsPenalized
64511:2:22< 10 MbpsPenalized
64511:2:23< 50 MbpsSlightly Favored
64511:2:24< 100 MbpsFavored
64511:2:29< 1 GbpsHighly Favored
64511:2:34≥ 1 GbpsHighest

Sample WireGuard + BIRD Config (for Peers)#

WireGuard (/etc/wireguard/wg-{peer}.conf)#

[Interface]# Your side — replace with your infoPrivateKey = <YOUR_PRIVATE_KEY>ListenPort = <YOUR_PORT>   # default: 2 + last 4 digits of your ASNAddress = <YOUR_DN42_IPv4>/32, <YOUR_DN42_IPv6>/128MTU = 1380
[Peer]# My side — replace endpoint with the node you are peering withPublicKey = <MY_PUBLIC_KEY>   # see node table aboveEndpoint = <NODE_ENDPOINT>:2xxxx   # my port, negotiated with meAllowedIPs = 0.0.0.0/0, ::/0PersistentKeepalive = 25

BIRD2 (/etc/bird/peers/as4242423777.conf)#

protocol bgp AS4242423777_AS4242423777 {    local as 424242xxxx;          # your ASN    neighbor <MY_DN42_IPV6>%<WG_IFACE> as 4242423777;    source address <MY_DN42_IPV6>;
    ipv4 {        extended next hop;        import all;        export filter {            # Example: tag your routes            # bgp_large_community.add((64511, 1, 2));  # <50ms latency            # bgp_large_community.add((64511, 2, 24));  # <100Mbps bandwidth            accept;        };    };
    ipv6 {        import all;        export all;    };}

How to Request Peering#

  1. Contact me via Telegram @cloudc001 or email cloudc001#outlook.com.
  2. Tell me:
    • Your ASN
    • Which of my nodes you want to peer with (pick the one with lowest latency for you)
    • Your WireGuard public key
    • Your DN42 IPv4 & IPv6 addresses
  3. I will reply with the corresponding node's Endpoint and Public Key.
  4. We exchange configs and bring up the session.

This document is generated for peering purposes. Please do not redistribute without permission.