Show Posts
1
20.7 Legacy Series / Re: Wireguard not working after upgrade.
« on: August 02, 2020, 11:59:45 pm »
I have the same issue. I had 11 endpoints, with local 10.0.0.x addresses and access to my local 10.10.10.x network, all working fine prior to upgrading.
After upgrade, the wireguard service shows as stopped in the dashboard. Additionally, none of the configurations or keys show in the "List Configurations" tab.
Logging into the console and running wireguard restart gives me this output:
root@OPNsense:~ # /usr/local/etc/rc.d/wireguard restart
wg-quick: `wg0' is not a WireGuard interface
INFO: (wg0) 2020/08/02 17:43:04 Starting wireguard-go version 0.0.20200320
I have re-installed the previous version of wireguard and restored my backup and all works as expected. If I upgrade, then it breaks.
Someone pointed out in another post that if the endpoints have two different networks shown in the allowed IP's field, then Wireguard will not start. Removing access to the local network WILL allow the configuration to display, but defeats the purpose of the VPN.
After upgrade, the wireguard service shows as stopped in the dashboard. Additionally, none of the configurations or keys show in the "List Configurations" tab.
Logging into the console and running wireguard restart gives me this output:
root@OPNsense:~ # /usr/local/etc/rc.d/wireguard restart
wg-quick: `wg0' is not a WireGuard interface
- wireguard-go wg0
INFO: (wg0) 2020/08/02 17:43:04 Starting wireguard-go version 0.0.20200320
- wg setconf wg0 /tmp/tmp.00CkDeZV/sh-np.us6fIr
- ifconfig wg0 inet 10.0.0.1/24 10.0.0.1 alias
- ifconfig wg0 mtu 1420
- ifconfig wg0 up
- route -q -n add -inet 10.0.0.5/32 -interface wg0
- route -q -n add -inet 10.0.0.4/32 -interface wg0
- route -q -n add -inet 10.0.0.3/32 -interface wg0
- route -q -n add -inet 10.0.0.25/32 -interface wg0
- route -q -n add -inet 10.0.0.24/32 -interface wg0
- route -q -n add -inet 10.0.0.2/32 -interface wg0
- route -q -n add -inet 10.0.0.13/32 -interface wg0
- route -q -n add -inet 10.0.0.12/32 -interface wg0
- route -q -n add -inet 10.0.0.11/32 -interface wg0
- route -q -n add -inet 10.0.0.10/32 -interface wg0
- route -q -n add -inet 10.10.10.0/24 -interface wg0
- rm -f /var/run/wireguard/wg0.sock
I have re-installed the previous version of wireguard and restored my backup and all works as expected. If I upgrade, then it breaks.
Someone pointed out in another post that if the endpoints have two different networks shown in the allowed IP's field, then Wireguard will not start. Removing access to the local network WILL allow the configuration to display, but defeats the purpose of the VPN.