mirror of
https://github.com/ergosteur/ergo-proxmox-scripts.git
synced 2026-10-28 13:00:37 -04:00
29d0a5b923e4ee5b4b36003c38293977750f4e79
Tailscale's UDP GRO forwarding tuning applies to the machine running tailscaled. That is VM 100 (ts-subnet-rtr), a KVM guest with its own kernel and netdevs, so ethtool on the Proxmox host cannot affect its forwarding path. Host-side tuning would only have been the right lever for a tailscaled running in an LXC container, which shares the host kernel. The interfaces were wrong in any case. VM 100 is on vmbr7, backed by enp4s0f7np7. vmbr0 is backed by enp4s0f0np0 and carries unrelated guests, and enp4s1f12np12 is the host's own routing NIC and not a bridge port at all. It never ran: the header says to run it from root's crontab, and root has no crontab. Both offloads were still off on every interface it named. Kept with a header recording where the tuning actually belongs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
Host-side tooling for a Proxmox VE node: cloud-init template building, IPMI fan control, UPS/NUT setup, and a few odds and ends.
131 KiB
Languages
Shell
90.1%
Python
9.9%