2.5Gb won’t be your bottleneck on the WAN side — 3-4TB a month is only about 10Mbps averge, and even torrent bursts won’t saturate that unless your internet is over a gig. The place I’d watch is traffic hairpinning through the router, like cameras and media going via OPNsense instead of staying on the switch — keep the NVR/Frigate traffic local where you can.
If you do virtualise it, the security bit that matters most is isolation: keep the WAN side separate from your media containers, and keep the Proxmox managment interface on the LAN only, not reachable from WAN. FYI, that’s also how a misconfigured bridge ends up exposing the host.
And keep your old Archer handy as a fallback router with the OPNsense config backed up — if Proxmox needs a reboot, you can swap one cable and be back online. YMMV, but for a house with 50 devices, I’d rather have that fallback than squeeze everything onto one box.
Comments
2.5Gb won’t be your bottleneck on the WAN side — 3-4TB a month is only about 10Mbps averge, and even torrent bursts won’t saturate that unless your internet is over a gig. The place I’d watch is traffic hairpinning through the router, like cameras and media going via OPNsense instead of staying on the switch — keep the NVR/Frigate traffic local where you can.
If you do virtualise it, the security bit that matters most is isolation: keep the WAN side separate from your media containers, and keep the Proxmox managment interface on the LAN only, not reachable from WAN. FYI, that’s also how a misconfigured bridge ends up exposing the host.
And keep your old Archer handy as a fallback router with the OPNsense config backed up — if Proxmox needs a reboot, you can swap one cable and be back online. YMMV, but for a house with 50 devices, I’d rather have that fallback than squeeze everything onto one box.
Sign in to comment. Sign in