MP-BGP
ENH (RFC8950)
Interval 2.5s, Multiplier 4
WireGuard Only
100 Mbit/s shaping both ways
DN42 registry objects mandatory
ROA required, invalid routes dropped
We use Large BGP Communities for traffic isolation and routing policy control. Routes are tagged on import. By default, only clean DN42 traffic is exported to standard peers.
| Community | Network Category | Export to Standard Peers |
|---|---|---|
(4242421013, 1000, 1) |
DN42 (172.20.0.0/14, etc.) | Permit (Transit) |
(4242421013, 1000, 2) |
Freifunk (10.0.0.0/8) | Drop |
(4242421013, 1000, 3) |
ChaosVPN | Drop |
(4242421013, 1000, 4) |
NeoNetwork | Drop |
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) |
Peers can use these Large Communities to influence routing decisions and traffic flows within our AS.
Note: Blackhole requests are strictly limited to single hosts (/32 for IPv4, /64-128 for IPv6).
| Community | Action | Description |
|---|---|---|
(4242421013, 0, 666) |
Blackhole | Drop traffic to destination |
(4242421013, 100, 50) |
Local_Pref 50 | Deprecated route |
(4242421013, 100, 100) |
Local_Pref 100 | Default routing preference |
(4242421013, 100, 200) |
Local_Pref 200 | Prioritize route (use as Primary link) |
You can use the template below to send a request via Telegram or Email:
Hi Naomu, I want to connect to your node: [Helsinki (fin) / Moscow (mow)] My side details: ASN: [Your AS number] Endpoint: [Your Clearnet Endpoint]:[WG Port] Public key: [Your WireGuard Public Key] Link-local: [Your IPv6 link-local] BFD: [Y/N] MTU: 1420 Kind Regards, [Your Name]