Proxmox

Proxmox VE’s networking layer is simple on the surface — bridges, bonds, VLANs — but there’s a gap between “it works” and “it’s maintainable.” A poorly planned bridge topology leads to broadcast storms, accidental cross-VLAN routing, or containers that can’t reach the internet because the bridge isn’t connected to anything. This post breaks down the networking setup on my Proxmox host (SRV1), which connects to a MikroTik router (R1) with VLAN filtering and a trunk port. By the end, you’ll know exactly how bridges map to the physical wire, how VLAN-aware bridges differ from the old approach, and how to assign VLANs to both VMs and LXC containers cleanly. ...

Frigate is an open-source NVR built for real-time object detection with local processing. No cloud subscriptions, no vendor lock-in — just cameras, a GPU, and decent detection models. This is how I set it up on my Proxmox host, with a Tapo C100 camera, Intel GPU inference via OpenVINO, MQTT eventing, and Telegram notifications. Architecture ┌──────────────┐ RTSP (stream1/stream2) ┌──────────────┐ │ Tapo C100 │ ───────────────────────────▶ │ Frigate │ │ 10.0.50.101 │ │ 10.0.20.15 │ └──────────────┘ │ │ CCTV VLAN (50) │ Web UI:5000 │ │ RTSP :8554 │ ┌──────────┐ │ WebRTC:8555 │ │ Telegram │ ◀──── MQTT events ──────── │ go2rtc:1984 │ │ alerts │ (frigate-notifier) │ API :8971 │ └──────────┘ └──────┬───────┘ │ ┌──────▼───────┐ │ Mosquitto │ │ MQTT:1883 │ └──────────────┘ The camera lives on VLAN 50 (CCTV). Frigate runs on a Debian LXC on VLAN 20 (LAB). The router’s firewall allows Frigate’s host (10.0.20.15) to reach the camera subnet — nothing else touches CCTV. ...