25.07.r.20250709.2036 First Boot WireGuard Service not running

Bob.Dig

I upgraded from 24.11 to 25.07 RC two times on the same machine (so far). Both times on the first boot one WG tunnel wasn't coming up and the service was reported as stopped. Both times, on the second boot the problem disappeared.
I will run RC now for more than a day and will report any findings.

stephenw10

Hmm, like one tunnel out of several didn't come up? But others did?

Bob.Dig

@stephenw10 Yes. From time to time I see a problem like this but not often. But here it was both times.

Bob.Dig

@stephenw10 Just upgraded to 25.07.r.20250715.1733, it happened again.

The problematic tunnel also is the same.

Another reboot fixes it.

Sidenote: I had uninstalled Nexus before but it was re-added on upgrading 25.07.r.20250715.1733.

stephenw10

Yes, Nexus is a default package in Plus, it should always be installed.

Bob.Dig

And it happened again. Tomorrow I will recreate this WG-interface just to make sure.

		<opt1>
			<descr><![CDATA[VPNcWgNtcpDirect]]></descr>
			<if>tun_wg7</if>
			<enable></enable>
			<spoofmac></spoofmac>
			<mtu>1420</mtu>
			<mss>1420</mss>
			<ipaddr>10.3.9.26</ipaddr>
			<subnet>29</subnet>
			<gateway>VPNcWgNtcpDirectGW</gateway>
		</opt1>

Bob.Dig

I had recreated the interface, also moving it away from being opt1. Today I wanted to try the if_pppoe kernel module. After the mandatory reboot, not only was the WireGuard Service down again, also none of the tunnels were up... I switched back to the old module after heaving no success with WireGuard after another reboot. But even then it took two further reboots to have WireGuard working again. Right now it works with the new module according to the web-UI but I am really concerned what will happen at next reboot.