Distillation

Date: Sep 17, 2026

• 🟡 (08:53) Host installation failed with install: cannot stat '/tmp/opencode/50-tailscale': No such file or directory; executing the unchanged persistence hook then produced netlink error: no device matches name (offset 24) and netlink error: No such device.
• 🟡 (08:53) Assistant identified that tmp/opencode/50-tailscale had been created only inside the tool’s isolated filesystem and was inaccessible as /tmp/opencode/50-tailscale from the user’s host. Consequently, the host file had not changed and still targeted nonexistent enp1s0.
• 🟡 (08:53) Assistant provided a direct host-side replacement procedure: printf '%s\n' \ '#!/bin/sh' \ 'set -eu' \ '' \ '/usr/sbin/ethtool -K br0 rx-udp-gro-forwarding on rx-gro-list off' \ | sudo tee /etc/networkd-dispatcher/routable.d/50-tailscale >/dev/null, followed by sudo chmod 755 /etc/networkd-dispatcher/routable.d/50-tailscale and sudo /etc/networkd-dispatcher/routable.d/50-tailscale.
• 🔴 (08:53) User reported the corrected /etc/networkd-dispatcher/routable.d/50-tailscale hook executed with no output, indicating success.
• 🟡 (08:54) Verification confirmed /etc/networkd-dispatcher/routable.d/50-tailscale is now an executable 4-line shell script containing #!/bin/sh, set -eu, a blank line, and /usr/sbin/ethtool -K br0 rx-udp-gro-forwarding on rx-gro-list off.
• 🟡 (08:54) Post-fix verification confirmed br0 had rx-udp-gro-forwarding: on and rx-gro-list: off; Tailscale health showed no warnings, connectivity remained healthy over direct UDP and IPv4/IPv6, and Linux 6.8 supports the optimization. The corrected persistent networkd-dispatcher hook targets br0; no further offload changes were needed.
• 🔴 (08:54) User stated the Tailscale machine labs was not always advertised as an exit node and wants it always advertised as one.
• 🔴 [requested-fix] (08:54) User asked the assistant to check and fix intermittent exit-node advertising on labs.
• 🟡 (08:54) Assistant noted current Tailscale status showed ExitNodeOption: true, meaning labs was advertising as an exit node at inspection time, and planned to inspect the live exit-node preference, tailscaled startup configuration, re-authentication history, and existing self-healing units to determine what event clears the setting and whether anything restores it.