


Running my own ASN from home: dual-WAN lab, MikroTik core, Proxmox cluster, and a /48 waiting to be announced
The centerpiece here isn’t the hardware. It’s that I’m standing up my own Autonomous System (ASN + IPv6 /48) to announce from home over BGP. Paperwork is signed. I’m waiting on the final invoice and my ISP’s go-ahead to light up the BGP session. The lab underneath already runs 24/7.
Connectivity
• WAN 1: ~900 Mbps (PPPoE)
• WAN 2: 150 Mbps symmetric, dedicated, with a /29 (3 usable public IPs)
• Dual-WAN in OpenWrt. One link for domestic, the other as the public/lab link
• Own ASN + IPv6 /48. Signed, BGP session pending
Network
• Router: TP-Link ER605 on OpenWrt. Dual-WAN (mwan3), SQM/cake on the public link
• Core switch: MikroTik CRS326-24G-2S+RM (24x GbE + 2x SFP+)
• Border/BGP router: still deciding between an RB5009 and an x86 mini-PC running VyOS/FRR. Opinions welcome
• Spares: Asus RT-AC1200, TP-Link Archer C64, T4U Plus USB adapter
Compute (Proxmox cluster)
• node1: i3 / 24 GB RAM. Always-on, runs the persistent services
• node2: powered up on demand for ephemeral labs (AD, deliberately vulnerable VMs)
• Raspberry Pi 3 as the QDevice for quorum
Workstations and misc
• MacBook Air M3, Asus VivoBook K3500P, ThinkPad E14
• PC #1: i5 / RTX 3060 / 32 GB / 256 GB SSD + 2 TB HDD, liquid cooled
• PC #2: i3 / GTX 1660 Ti / 16 GB / 256 GB SSD + 1 TB HDD
• 2x ESP32 + LoRa RYRR30D, still in the someday pile
Services running now
• AdGuard Home for network-wide DNS filtering
• Tor middle relay
• Prometheus + node_exporter + Grafana, alerting to Discord
• RIPE Atlas probe, spinning up
• The usual *arr media stack
• Considering a low-power SBC as a dedicated contribution node (Tor + RIPE Atlas + NTP)