The truecommand service is failing to start the wireguard service after is receives an Active state from the portal. Attached is a customer debug that demonstrates this issue, leading to continual reboots until the interface is disabled. Notice the wg0 interfaces messages in logs, as well as the number of processes associated with wg-quick up. Looks like it’s trying to start the service every 3s.

This has been seen since at least U1, but I’ve made some leads on how to reproduce this. I enabled verbosity on wsdd and removed the monitoring daemon from starting with wg-quick. The daemon seems unreliable and doesn’t exist on Linux. I noticed the loop starting once I restarted the wireguard interface without the monitoring daemon, although I don’t know if that is what triggered it or what is preventing the extra processes from summoning.

I’ll also mention that you can manually up/down the interface during this and it’ll keep looping. This also causes the UI to hang if you try to disconnect from TC.