dev/nixfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
master
nixfiles/docs/remote/britway.md
T
jackos1998 08605ab422 docs/boxes: Prioritize hardware details 
Place physical hardware inventories and VPS resource allocations near
the top of each box page, while leaving broader platform details in
their topical sections.
2026-08-02 00:23:30 +01:00

2.8 KiB
Raw Permalink Blame History

britway

A Vultr VPS in London (lon1) acting as the network edge node: the self-hosted Tailscale control plane, a tailnet exit node, and the BGP speaker for AS211024.

Platform

Component Allocation
Virtualisation Vultr VC2 virtual guest on a QEMU-compatible platform
Compute 2 vCPUs and 2 GiB RAM
Storage 65 GiB virtio disk with separate ext4 filesystems for /boot, /nix and /persist; root is tmpfs

Role

  • Headscale — the self-hosted Tailscale control plane at hs.nul.ie; every other box's tailscaled logs in here (--login-server=https://hs.nul.ie). Google OIDC for auth, SQLite state, MagicDNS under ts.nul.ie, and split DNS pointing the colony/home domains at their internal resolvers.
  • Tailscale exit node — advertises --advertise-exit-node plus routes to the home v4/v6 prefixes; tailnet traffic is SNATed out veth0 (v4 to the Vultr public IP, v6 to the as211024 mesh address).
  • BGP edge — bird2 speaks BGP as AS211024 to Vultr transit (AS64515, separate v4/v6 sessions authenticated with a password from britway/bgp-password-vultr.conf) and exports everything to a bgp.tools monitoring session. It originates the internal, colony and home IPv6 prefixes documented in networking.
  • nginx — reverse proxy fronting headscale (hs.nul.ie → localhost headscale port), with a wildcard ACME cert for nul.ie issued via Cloudflare DNS.

Network assignments

See the consolidated network assignments table (this box: britway).

Networking

  • Two assignments: vultr on the provider interface veth0 (renamed by MAC), and as211024 on the l2mesh VXLAN interface (my.vpns.l2) — member of the shared mesh (see The AS211024 L2 mesh).
  • Static routes steer colony/home v4 traffic over the as211024 mesh. A separate ts-extra routing table with a policy rule on tailscale0 ingress sends Tailscale-sourced v6 traffic for colony via estuary, while the box's own v6 uses WAN.
  • The firewall trusts the as211024 prefixes (lib.my.c.as211024.nftTrust) and tailscale0; iperf3 runs with an open port for bandwidth testing.

Notable config files

Reference in New Issue View Git Blame Copy Permalink