Tunnel to Mullvad suddenly won't connect

Started by vorago, January 23, 2023, 06:12:47 PM

Previous topic - Next topic
Hello,

Sometime last night my 3 tunnels to Mullvad all died for reasons I can't figure out and now they refuse to connect. They had been working fine for months prior to this.

I've rebooted, disabled all but 1 tunnel, and have tried using a different server than before. My subscription is still active. Which logs can I look at that might give me an idea of what's going wrong?

January 23, 2023, 06:21:24 PM #1 Last Edit: January 23, 2023, 06:24:23 PM by vorago
Actually, I think these lines from System: Log Files: General might hint at it.

/usr/local/etc/rc.routing_configure: The command '/sbin/route add -'inet' '10.66.XX.XX' -interface 'wg2'' returned exit code '65', the output was 'route: interface 'wg2' does not exist'
/usr/local/etc/rc.routing_configure: The command '/sbin/route add -'inet' default '10.66.XX.XX'' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add net default: gateway 10.66.XX.XX fib 0: Network is unreachable'


The sole interface I'm leaving enabled is wg4 though, so I'm not sure why that message is popping up.

January 23, 2023, 08:35:04 PM #2 Last Edit: January 23, 2023, 08:40:41 PM by vorago
I noticed that a small update was available, one of which was the wireguard-kmod to 0.0.20220615_1. Took that then rebooted and now things are connected. Guess that answers that.