FurrIX Peering Policy
Virtual Internet Exchange – Hobbyist Community Network
Autonomous System: AS218034 [AS-MAWS-N-PAWS]
(Last Updated: November 18, 2026)

1. About FurrIX
FurrIX is a community‑run hobbyist network built by hobbyists, for hobbyists.
We operate as an independent network for experimentation, learning,
interconnecting independent labs, research environments and alternative
network spaces. Everything is volunteer‑operated, best‑effort and powered
by people participating for curiosity and passion.

1.1 Maws N Paws (maws-n-paws.exchange)
The network that FurrIX operates is named “Maws N Paws” and runs under the
namespace ‘maws-n-paws.exchange’. FurrIX operates and governs the network
as a shared clubhouse resource for both peers connecting to us and our internal
members who are being bootstrapped by us.

2. Peering Overview
FurrIX supports lightweight, settlement‑free peering with fellow hobbyists, researchers
and interested network operators who wish to interconnect for experimental or
collaborative purposes.

Transport and Connectivity
Access Method:
Peers connect to FurrIX via WireGuard to either of our edge routers. Our network core
and primary edge is located in KC, MO, USA with our secondary edge being located in
Dus, Germany. When wishing to peer with us, please let us know which edge you are
closer to so that we can make sure we activate the correct endpoint.

Interconnect Addressing:
Point-to-point links utilize either a mutually agreed‑upon GUA /127 or ULA /127
assigned by either FurrIX or the peer.

Protocol Scope:
WireGuard transport may run over IPv4 or IPv6, but traffic inside the tunnel is
strictly IPv6-only. IPv4 announcements and payloads are dropped at the border.
FurrIX does not handle IPv4 internally.

ASN Usage:
FurrIX operates using AS218034 for all BGP sessions with peers external to our
network. We do not support private ASN peering externally.

Peering Types:
Currently FurrIX only supports BILAT peering, in which we directly connect and exchange
routes with one another without the use of a route server.

3. Routing and Prefix Policies
To maintain stability across our edge, strict prefix policies are enforced on all BGP sessions:
- Origin Enforcement: Both networks must announce only IPv6 prefixes they personally
operate and originate. Third-party prefixes, default routes (::/0) and unowned blocks
are strictly prohibited.

- Prefix Size Limits: To match standard Internet engineering practices, FurrIX will not accept
announcements smaller than a /48 (e.g., /49, /56, /64 route injections are rejected).

- Prefix Count Limit: FurrIX enforces a limit of up to ten (10) IPv6 prefixes per peer across
all sessions, keeping configurations manageable for a volunteer-run team.

- Policy Filtering: Both sides are expected to design and apply explicit prefix-lists and
route-maps to restrict BGP exchanges strictly to agreed-upon prefixes. Any announced
prefixed not agreed upon are dropped.

4. Traffic Expectations
Peering with FurrIX is strictly settlement‑free and bilateral. FurrIX does not provide commercial
transit, paid guarantees or SLAs. Inter-exchange traffic is exchanged purely for collaboration,
the love of the craft and learning. WireGuard peering links are not engineered for sustained,
high-volume saturation. Peers must keep traffic at reasonable levels so neither network’s
infrastructure is adversely affected.

Peers will have reachability to FurrIX’s own prefixes, such as our 2602:f992:e0::/44 and
2a0c:b641:1030::/44 blocks.

5. Operational Expectations
FurrIX is a volunteer‑run hobbyist network with limited resources and no guaranteed uptime.
Maintenance, upstream shifts, route changes or real‑world events may affect availability at
any time. FurrIX reserves the right to pause, filter or terminate any BGP session or peer
connection immediately if traffic causes instability, violates network policy or constitutes abuse.

Inquiries:
For peering, routing or NOC coordination: noc@furrix.zone
For support or general coordination: support@furrix.zone