Naomu Network

AS4242421013

Looking Glass: lg.naomu.dn42

Peering Policy & Specs

Routing Protocol

MP-BGP

BGP Feature

ENH (RFC8950)

BFD (Optional)

Interval 2.5s, Multiplier 4

Tunnel Type

WireGuard Only

Valid Registry Objects

DN42 registry objects mandatory

Routing Security

ROA required, invalid routes dropped

BGP Routing Policy & Communities

1. Ingress Telemetry (Large Communities)

We tag all imported routes with informational Large BGP Communities to identify entry point topology, geolocation, and ingress peer identity across our network.

Community Category Description & Format
(4242421013, 1, <Country>) Ingress Country ISO 3166-1 numeric code (e.g. 246 for FI, 643 for RU)
(4242421013, 2, <PoP_ID>) Ingress Metro / PoP Site identifier (e.g. 1001 = HEL, 1002 = MOW, 1003 = SPB, 1004 = SPB1)
(4242421013, 3, <Node_ID>) Ingress Router Specific border gateway instance ID (e.g. 1 = MOW Core, 2 = HEL Core, 3 = SPB1 Node, 4 = SPB Node)
(4242421013, 4, <Peer_ASN>) Learned From Peer Full 32-bit ASN of the adjacent peer from whom the route was directly accepted

2. Informational Metrics (Standard Communities)

We fully support standard DN42 communities (64511:X). Link metrics are automatically calculated and propagated. Geo-location tags are applied only to our originated prefixes.

Community Type Description
(64511, 1..9) Latency Dynamically updated per peer
(64511, 21..29) Bandwidth Dynamically updated per peer
(64511, 31..34) Crypto Dynamically updated per peer
(64511, 41) Geo-Region Europe (Origin only)
(64511, 1643) / 1246 Geo-Country Russia / Finland (Origin only)

3. Traffic Engineering (Action Communities)

Peers can use these Large Communities to influence routing decisions and traffic flows within our AS.

Community Action Description
(4242421013, ---, ---) TE Temporarily not working

4. Dynamic Path Scoring & Route Selection

We implement an automated Performance-based Routing (PbR) engine. Every route imported into our AS is scored deterministically by calculating bgp_local_pref in real-time based on active link latency (RTT probing), AS-Path length, and peer tiering.

local_pref = Peer_Tier - (Link_RTT_Bucket * 20) - (AS_Path_Len * 45) + Direct_Peer_Bonus - iBGP_Transit_Penalty
Peer Tier Base Metric Qualification
Tier 1 (Core) 860 Major regional backbones, IXP presence, datacenter nodes
Tier 2 (Standard) 800 Default tier applied to all regular peerings
Tier 3 (Edge) 740 High jitter connections, home routers, or backup tunnels
Adjustment Factor Weight Technical Reason
Direct Peering Bonus +150 Applied to directly connected peers (AS-Path = 1) to prevent tromboning
Peer Link RTT Penalty -20 / bucket Subtracted per logarithmic latency bucket (64511:1..9) via background probing agent
AS-Path Length Penalty -45 / hop Deducted per AS hop (bgp_path.len * 45) to penalize long overlay paths
iBGP Transit Penalty -35 Deducted across backbone mesh to favor local border egress over remote hub transit

Network Nodes

๐Ÿ‡ซ๐Ÿ‡ฎ Helsinki, FI
Upstream: AS215730 (H2 Nexus)
Aggregate Bandwidth: 1 Gbps
Transit: Native IPv4/IPv6
Endpoint (clearnet): fin.dn42.naomu.net
Endpoint (DN42): fin.srv.naomu.dn42
WG Public key: GpmoYiwzeAyrdm2uVoiWtu2heateEb2fO2TBPXp4wCk=
WG Port: 2+ last 4 digits of your ASN (i.e. 21013)
IPv6 link-local: fe80::1013
Disallowed Ingress: RU
๐Ÿ‡ท๐Ÿ‡บ Moscow, RU
Upstream: AS29182 (JSC IoT)
Aggregate Bandwidth: 250 Mbps
Transit: Native IPv4/IPv6
Endpoint (clearnet): mow.dn42.naomu.net
Endpoint (DN42): mow.srv.naomu.dn42
WG Public key: bd0uTqnf13yIpTNcvh+f4q2bXR5hw/EJ92m7n3rv2yk=
WG Port: 2+ last 4 digits of your ASN (i.e. 21013)
IPv6 link-local: fe80::1013
๐Ÿ‡ท๐Ÿ‡บ Saint-Petersburg, RU
Open peering is unavailable. If needed, please contact us to explain why you need peering in St. Petersburg.
๐Ÿ‡ท๐Ÿ‡บ Novosibirsk, RU
Upstream: AS57494 (Adman LLC)
Aggregate Bandwidth: 100 Mbps
Transit: Native IPv4/IPv6
Endpoint (clearnet Only IPv4): nsk.dn42.naomu.net
Endpoint (DN42): nsk.srv.naomu.dn42
WG Public key: 0McodPZjj39iZshntGhYxSz8YrjiVqL321FRjur5rQA=
WG Port: 2+ last 4 digits of your ASN (i.e. 21013)
IPv6 link-local: fe80::1013

ะ ัƒััะบะพัะทั‹ั‡ะฝั‹ะน ั‡ะฐั‚ DN42 ะฒ Telegram: @dn42dev

Request Example

Peering Request / Contacts