Frequently asked questions

Quick answers to the questions we hear most. If something isn't covered here, get in touch and we'll be happy to help.

Getting started

What is RoutedBits?

RoutedBits is a hobby network run by a small group of professional network engineers, using DN42 as a platform to experiment with service-provider-style routing, automation, and emerging technologies. See the Overview for the full picture.

Who can peer with RoutedBits?

Any registered DN42 member in good standing. You'll need a DN42 registry presence — a registered ASN and maintainer object (MNT) — and a WireGuard endpoint of your own.

Does peering cost anything?

No. RoutedBits is a non-commercial hobby project, and there is no charge to peer with us.

How do I request a peering?

Sign in with the Log in with Kioubit button, then go to Peerings → Add peering and fill in your side of the tunnel. Our automation provisions the RoutedBits side and brings up the session. See Requesting a peering for a walkthrough.

How long until my session comes up?

Usually within 5–10 minutes of submitting the form. Live details appear on the peering page as metrics begin to arrive.

Sessions & configuration

Which node should I peer with?

Pick the node closest to you for the best latency. The Nodes page lists every location along with its address-family support and endpoint.

Can I peer with more than one node?

Yes. You can set up a session on each node you'd like to peer with — just add a separate peering for each one.

Do I need both IPv4 and IPv6?

At least one BGP session (IPv4 or IPv6) is required; you're welcome to run both. You can also carry both families over a single session with Multi-protocol, or advertise IPv4 over an IPv6 next hop with Extended Next Hop. Every option is described on the Session options page.

What address should I use for the tunnel?

Your IPv4 tunnel address must be within DN42 space (172.20.0.0/14) and belong to your ASN's allocation. For IPv6, a link-local address (fe80::/10) is preferred — for example fe80:: followed by the last four digits of your ASN.

What WireGuard settings does RoutedBits use?

Once you submit, we generate the RoutedBits side of the tunnel — endpoint (hostname.routedbits.com:[port]), our public key, and BGP peer addresses. Set your tunnel MTU to 1420. All of these details are shown on your peering list and the live session status page.

Can I change or remove a peering later?

Yes. Open the peering from your list to edit its settings or delete it at any time.

Routing & filtering

How are my routes filtered?

Prefixes must fall within DN42 address space and pass RPKI origin validation. Valid routes are announced, invalid routes are rejected, and unknown routes are kept at a lower local preference but not advertised outside of RoutedBits. Full details are on the ROA & route filtering page.

Why isn't my prefix being accepted or propagated?

The most common causes are a prefix outside DN42 address space, or one without a matching ROA in the DN42 registry. Confirm your prefix is registered to your ASN with a correct ROA so it validates as Valid.

Can I influence how my routes are handled?

Yes. Attach BGP large communities to your announcements for actions like AS prepending, blackholing, or limiting propagation to specific regions. See BGP communities for the full list.

Why does my traceroute look weird?

RoutedBits forwards traffic over a Linux-based SRv6 (Segment Routing over IPv6) underlay. Linux currently lacks the extensions needed to correctly expose SRv6 paths to traceroute, so intermediate hops don't respond as they normally would. As a result, a traceroute across our network won't show the router you peer with (the entry router) or any underlay hops in between — only the exit router where traffic leaves toward its destination. Seeing just the exit router, rather than the router you peer with, is expected and not a sign of a problem.

Operations & support

What platform do your routers run?

A customized version of VyOS. We contribute bug fixes and features upstream so the wider community benefits from our improvements.

Why was my session removed automatically?

Sessions are monitored continuously. A peering may be removed automatically if its WireGuard endpoint stops resolving in DNS, or if the BGP session never establishes or stays inactive past our threshold. You'll see warnings on the session status page before this happens.

How do I report abuse or get support?

Email [email protected], or use the contact page. For abuse reports, please include the details listed in our Abuse Policy.