Public operations repository for AS215932 (Hyrule/Servify) - building a complete Internet Service Provider from scratch.
AS215932 is a solo project to build and operate a full-stack ISP with modern BGP routing, multi-homing, and IPv6-first architecture. This repository tracks infrastructure work, configuration management, and operational decisions.
Working in public to share knowledge with the networking community and demonstrate real-world ISP operations.
- ASN: AS215932
- Network Name: Hyrule / Servify
- NOC: noc@as215932.net
- Peering Policy: Open (see PeeringDB)
- PeeringDB: AS215932
- Multiple BGP transit providers
- Presence at multiple Internet Exchange Points (IXPs)
- IPv6-only (for now, hopefully forever unless I can't avoid it)
- RPKI ROA configured
- IRR objects registered (RIPE Database)
AGENTS.md is the canonical domain-policy reference for this repo. In short:
hyrule.host is customer-facing Hyrule Cloud identity, servify.network is
infrastructure identity, and as215932.net is AS215932 overlay/routing identity
only.
Active IXP presence at multiple locations - see PeeringDB for current list
- Core Routers: FreeBSD + FRRouting
- Edge Router: Debian 13 + FRRouting (rtr at OVH)
- Overlay Network: Wireguard tunnels
- Protocols: BGP, OSPFv3
- Virtualization: XCP-NG w/ Xen Orchestra
- IPv6-first design with IPv4 transition mechanisms (NAT64/DNS64, 464XLAT)
- Multi-homed BGP (with ECMP load balancing)
- Stateless overlay for asymmetric routing
- Distributed routing architecture with OSPF internal connectivity
network-operations/
├── autoinstall/ # OS autoinstall configs and QMP tools
├── configs/ # Configuration templates (Jinja2)
├── docs/ # Architecture and deployment documentation
├── scripts/ # Bootstrap and operational scripts
└── .github/ # Issue templates and workflows
I maintain an open peering policy and welcome peering requests at any of my IXP locations.
Peering Requirements:
- Valid entry in PeeringDB
- IRR objects registered
- 24/7 NOC contact
- RPKI ROA configured
Contact via PeeringDB or open an issue in this repository with the peering label.
Key documentation:
- Obtain AS number and IP allocations
- Establish BGP transit agreements
- Deploy at Internet Exchange Points
- Complete PeeringDB and IRR registration
- Implement core routing infrastructure
- Expand IXP presence
- Grow peering relationships
- Deploy additional services (Tor/I2PD/Yggdrasil relays, public resolvers, etc.)
- x402 one-time service usage (like paying for one tor request)
- Automate configuration management
- Build comprehensive monitoring stack
This repository serves as:
- Issue tracker for infrastructure work and bugs
- Configuration library for reusable network configs
- Documentation hub for architecture and procedures
- Public record of network operations and decisions
Feel free to:
- Browse issues to see ongoing work
- Learn from configuration examples
- Open issues for peering requests or questions
- Contribute suggestions or report issues
- NOC Email: noc@as215932.net
- PeeringDB: https://www.peeringdb.com/asn/215932
- Issues: Use GitHub Issues for operational questions or peering requests
License: Configuration examples and documentation in this repository are provided as-is for educational purposes.
Building the Internet, one BGP session at a time.