[6.12.1] Wireguard deactivates itself after about 1 minute.

Try the following:

- Stop the WG tunnel

- Make a dummy configuration change to force an update

- Start the WG tunnel

 

adjusted rule on local firewall tunnel to deny, clicked apply, then changed back to allow and clicked apply and restarted the tunnel, no improvement.

 

attached are recent diags from change

chipshop-diagnostics-20230623-1905.zip

Edited June 23, 2023 by OmegaXis
add diag

My two servers each are up for almost 24 hours, and so are the wireguard tunnels on them.

 

I'll have a look at your diagnostics.

 

Your wireguard tunnels use IP addresses in the same range as your LAN network (192.168.126.x), that gives conflicts.

The default WG network is 10.253.0.0 and is recommended to use.

 

my lan is 192.168.128.x

Edited June 23, 2023 by OmegaXis
add photo of default lan settings

16 minutes ago, OmegaXis said:

my lan is 192.168.128.x

 

Sorry misread 6 and 8.

 

In your log file the following is happening each time the WG tunnel is started

Jun 23 15:03:23 chipshop wireguard: Tunnel WireGuard-wg0 started
Jun 23 15:03:25 chipshop vnstatd[7491]: Interface "wg0" enabled.
Jun 23 15:03:35 chipshop vnstatd[7491]: Interface "wg0" disabled.

 

Remove the networkstats plugin and retest

Or start your system in safe mode and retest

 

Test ran and plugin removed, no improvement, attaching new logs

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.126.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 192.168.126.3/32 dev wg0
[#] ip -4 route add 192.168.126.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started';/usr/local/emhttp/webGui/scripts/reload_services
Terminated
[#] ip link delete dev wg0
Unable to access interface: No such device
[#] ip link delete dev wg0
Cannot find device "wg0"

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.126.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 192.168.126.3/32 dev wg0
[#] ip -4 route add 192.168.126.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started';/usr/local/emhttp/webGui/scripts/reload_services
Terminated
[#] ip link delete dev wg0
Unable to access interface: No such device
[#] ip link delete dev wg0
Cannot find device "wg0"

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

in between the two tests of wireguard shown here i adjusted NAT (Turned on NAT, clicked apply, activated tunnel, waited for deactivation, Turned off NAT, clicked apply, turned on tunnel, waited for deactivation.)

 

Attached are new diags from most recent test.

 

chipshop-diagnostics-20230623-1958.zip

The plugin is still active in your latest diagnostics.

 

Start your system in safe mode to rule out any plugin.

 

Safe mode on, issue is still persistent. As usual, new logs attached.  Additionally same testing methodology of toggeling NAT was preformed again.

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.126.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 192.168.126.3/32 dev wg0
[#] ip -4 route add 192.168.126.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started';/usr/local/emhttp/webGui/scripts/reload_services
[#] iptables -t nat -A POSTROUTING -s 192.168.126.0/24 -o br0 -j MASQUERADE;iptables -N WIREGUARD_DROP_WG0;iptables -A WIREGUARD -o br0 -j WIREGUARD_DROP_WG0;iptables -A WIREGUARD_DROP_WG0 -s 192.168.126.0/24 -d 192.168.128.1 -j ACCEPT;iptables -A WIREGUARD_DROP_WG0 -s 192.168.126.0/24 -j DROP;iptables -A WIREGUARD_DROP_WG0 -j RETURN
[#] ip -4 route flush table 200
[#] ip -4 route add default via 192.168.126.1 dev wg0 table 200
[#] ip -4 route add 192.168.128.0/24 via 192.168.128.1 dev br0 table 200

wg-quick up wg0

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

wg-quick down wg0

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.126.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 192.168.126.3/32 dev wg0
[#] ip -4 route add 192.168.126.2/32 dev wg0
[#] logger -t wireguard 'Tunnel WireGuard-wg0 started';/usr/local/emhttp/webGui/scripts/reload_services
Terminated
[#] ip link delete dev wg0
Unable to access interface: No such device
[#] ip link delete dev wg0
Cannot find device "wg0"

wg-quick down wg0
wg-quick: `wg0' is not a WireGuard interface

 

chipshop-diagnostics-20230623-1632.zip

With tunnels are autostarted I don't have a problem, tunnels stay active all the time, but when making changes I can replicate your issue. Need to further investigate why this happens.

 

Thx

 

In my testing I do the following:

 

- WG tunnel is active

- Make a change (NAT rule)

- Apply, and then afterwards tunnel goes down (this is unexpected)

- Re-activate tunnel and second time it stays up

 

I dont have it stay up the second time. It still goes down. doesnt matter how many times I reactivate it.

 

This tunnel is important to me as it's how I access my home lab for proof of concept stuff for work.  What are the chances of this getting resolved soon?

Edited June 24, 2023 by OmegaXis

At this point, i am reverting back to 6.11.5, the entire server has become slow and unresponsive, ill try 6.12 again maybe when 6.12.2 comes out. There are just too many instabilities for a piece of paid software.

 

Cant even downgrade. went to try and only 6.12 is an option.

 

 

Edited June 25, 2023 by OmegaXis

5 hours ago, OmegaXis said:

 

Cant even downgrade. went to try and only 6.12 is an option.

 

You can always use the Manual method described here in the online documentation.

I am also having this issue.  Here are my diagnostics.  

nas1-diagnostics-20230625-1357.zip

23 minutes ago, sittingmongoose said:

I am also having this issue. 

 

I don't see this problem in your diagnostics.

Next release has an update to solve a race condition when a wireguard tunnel is updated.

Please retest when it is available.

 

6 minutes ago, bonienl said:

 

I don't see this problem in your diagnostics.

Next release has an update to solve a race condition when a wireguard tunnel is updated.

Please retest when it is available.

 

Any idea when the next release is due?

Soon (tm)

It is currently going thru internal testing.

 

Is there a means to sign up to beta test it if not I'll wait until it comes out and try again I'm back on 6.12.0 and currently stable 

Solved via update to 6.12.2

Changed Status to Solved