Past three devices, ssh everywhere becomes unmaintainable. Portainer’s Edge Agent mode pulls them into one control plane. Think in fleets, not boxes Edge Agent architecture: a light agent per device; the control plane tunnels config down, so no device ports are exposed; Reusable stacks: one compose definition pushed to many devices, parameterized per site; Permission […]
Throughput shortfalls can live in any layer — physical, driver, kernel stack or application — so measure each. Find the bottleneck layer by layer Physical and driver: confirm negotiated speed with ethtool and check error counters with ethtool -S; Kernel parameters: raise rmem/wmem maxima, netdev_max_backlog and tcp_rmem, and use parallel streams to saturate the link […]
The value of a data gateway is one box talking to every PLC on site, which demands broad protocol coverage and tag-list configuration. Multi-protocol is the bulk of the work Protocol coverage: S7, MC, FINS and Modbus TCP are the big four — build a compatibility matrix and test unit by unit; Tag lists: import […]
The client required that nothing in the rooms stop working when the WAN drops, which pushed the architecture from cloud to local edge. Local-first was non-negotiable Architecture: one edge host per floor running Home Assistant, room devices on Zigbee and Bluetooth, with the gateway only for remote access and configuration; Network: guest Wi-Fi separated from […]
Cleartext DNS exposes every domain you visit and can be hijacked. Encrypted upstreams fix both at once. Why encrypt DNS AdGuard Home speaks DoH/DoT: paste upstream URLs; latency usually grows under 5 ms; Split routing: low-latency upstream for local domains, encrypted general upstream for the rest; Enforce it: point DHCP at the RK3588 and block […]
Before DDNS, identify your egress: public IPv4, IPv6-only, or carrier NAT — the answers differ completely. First, know what you have Public IPv4: a single ddns-go container polls the interface and updates dozens of DNS providers; IPv6-only: home prefixes rotate; ddns-go tracks the v6 address and clients must reach v6 directly; No public IP: DDNS […]
MQTT is the nervous system of a smart home, yet most guides stop at “install and go”. An unauthenticated broker becomes a liability the moment an untrusted device joins. The bus needs permissions too Enable password files and listeners: two accounts — sensors publish-only, controllers subscribe; Isolate by topic prefix: zigbee2mqtt/# writable only by Z2M, […]
The key metrics are NAT throughput, concurrent connections and offload capability; clock speed is not the first priority. Routers are judged on forwarding, not benchmarks RK3528’s place: quad A53 with dual gigabit, low power and good cost for home and small business routing; RK3568’s edge: richer PCIe and USB3 for Wi-Fi 6 modules or multi-port […]
Port chaos follows service sprawl. A reverse proxy with a single 443 entry and host-based routing is the cleanest structure. One entry for all services Deploy: the jc21/nginx-proxy-manager three-container stack, publishing 80/443; Certificates: built-in Let’s Encrypt renewal; wildcard certs need DNS validation (one API token covers a year); Security: expose only 443 and bind the […]
Linux lands most interrupts on CPU0 by default, leaving one core saturated while others idle and total throughput capped. Interrupts defaulting to CPU0 is the trap Inspect: cat /proc/interrupts shows which core each IRQ lands on — watch NIC and storage controllers; Pin them: set /proc/irq//smp_affinity to spread NIC interrupts across the A76 cores; Pair […]