JerryXiao’s DN42 Network

Aka Jerry Network

We are

AS4242423618

AS4201270006

Peering Policy

New peers are always welcome.

Currently only wireguard, gre/plain, vxlan tunnels are permitted.

Inactive peers may be removed after a certain amount of time.

Excessive amount of transit traffic is not allowed.

Jerry Network has two kinds of nodes (see node info below), one with open peering policy and the other with selective peering policy. Peering with selective nodes requires additional steps of validation.

To establish a peer with me, send an email to [email protected]

The following information is required:

Your ASN (DN42)
One of my two asns of your choice (4242423618 / 4201270006)
The node you would like to peer
Your wireguard public key
Your tunnel link addresses
Your tunnel endpoint (optional)
Your tunnel mtu (optional, default 1420)

Our forwarding plane support both IPv4 (172.20.0.0/14, 172.31.0.0/16, 10.0.0.0/8) and IPv6 (fd00::/8). Control plane (bird2) has the following capabilities enabled: multiprotocol IPv4/IPv6 unicast, extended nexthop (RFC 5549) and extended message (RFC 8654).

We are in favor of multiprotocol bgp sessions via IPv6 link local with extended nexthop enabled (BGP unnumbered). However, other configurations are also acceptable. Peers with no public endpoints are welcome, just a note that you may want to set the persistent-keepalive attribute of your wireguard tunnel to a reasonable value.

Node information

sjc1.us.jerry.dn42

Identifier	sjc1.us.jerry.dn42
Location	San Jose, CA, USA
Peering Policy	Open
Tunnel Endpoint	us.neo.jerryxiao.cc:<port> *
DN42 address	172.20.51.112 fd07:d34:7969:200::1
NeoNetwork address	10.127.8.208 fd10:127:53:200::1

ams1.nl.jerry.dn42

Identifier	ams1.nl.jerry.dn42
Location	Amsterdam, Netherlands
Peering Policy	Open
Tunnel Endpoint	nl.neo.jerryxiao.cc:<port> *
DN42 address	172.20.51.120 fd07:d34:7969:100::1
NeoNetwork address	10.127.8.216 fd10:127:53:100::1

hk1.cn.jerry.dn42

Identifier	hk1.cn.jerry.dn42
Location	Hong Kong, China
Peering Policy	Selective
Tunnel Endpoint	hidden
DN42 address	172.20.51.98 fd07:d34:7969:1::1
NeoNetwork address	10.127.8.194 fd10:127:53:1::1

hk2.cn.jerry.dn42

Identifier	hk2.cn.jerry.dn42
Location	Hong Kong, China
Peering Policy	Selective
Tunnel Endpoint	hidden
DN42 address	172.20.51.100 fd07:d34:7969:3::1
NeoNetwork address	10.127.8.196 fd10:127:53:3::1

sh1.cn.jerry.dn42

Identifier	sh1.cn.jerry.dn42
Location	Shanghai, China
Peering Policy	Selective
Tunnel Endpoint	hidden
DN42 address	172.20.51.99 fd07:d34:7969:2::1
NeoNetwork address	10.127.8.195 fd10:127:53:2::1

tyo1.jp.jerry.dn42

Identifier	tyo1.jp.jerry.dn42
Location	Tokyo, Japan
Peering Policy	Selective
Tunnel Endpoint	hidden
DN42 address	172.20.51.97 fd07:d34:7969::1
NeoNetwork address	10.127.8.193 fd10:127:53::1

* Wireguard endpoint ports are dynamically assigned.

Unique Wireguard Keypairs are generated for every peer.

IPv6 link local address defaults to fe80::3618/64

BGP Communities

The following well-known BGP communities are supported:

Community	Description	Action
(65535:65281)	No Export	Prefix should not be exported outside of the AS
(65535:65282)	No Advertise	Prefix should not be exported to any peers
(65535:666)	Blackhole	Prefix is blackholed and should not be exported outside of the AS

The following DN42 communities are supported:

Community	Description
(64511:0<x<21)	Max latency
(64511:20<x<30)	Min bandwidth
(64511:30<x<35)	Min encryption
(64511:40<x<54)	Route Origin

The following large communities are used:

Large Community	Description
(4242423618:1:x)	Translated DN42 region community with ISO 3166-1 country code x // 1000 equals the standard DN42 region community x % 1000 equals the ISO 3166-1 country code
(4242423618:120:x)	On which node the route is received
(4242423618:140:x)	In which region and country the route is received Same format as (4242423618:1:x)

Routing Policy

Jerry Network implements a series of import filters which alters local_pref for better route selection around the globe. Since this method relies heavily on region communities, routes without the correct communities are almost not optimized. We strongly recommend all of our peers to adopt those bgp communities for better network performance.

When several routes are available to a single destination, the following mechanism is used to determine which one is the best.

When the AS path length is bigger than 5, subtract 5 from the local_pref
When the AS path length is bigger than 3, subtract 3 from the local_pref
When the AS path length is bigger than 1, subtract 1 from the local_pref
When the AS path length is 1, add 1 to the local_pref
When a route with a path len bigger than 1 has a latency community (64511:1) to (64511:9) as (64511:x), subtract (x-1) from the local_pref
When a route with a path len bigger than 1 has a unencrypted tunnel community (64511:31) or (64511:32), subtract 1 from the local_pref
When a route is originated in China, and learned on one of my nodes in China, add 100 to the local_pref
When a route is originated in a certain region, and learned on one of my nodes in that same region, add 2 to the local_pref
When a route has a originate region, add a certain number (from 0 to 20) to the local_pref, that number reflects the typical latency from the current router to the destination region.

Note that if a route has no region communities, the last three rules are not invoked.

Routes inside the same region are always preferred, even if a much longer AS path is observed.