WireGuard suddenly stopped working between Beryl and Slate routers

Routers
1

Moved abroad for wife’s work, was allowed to work remotely for my job but to access firm’s intranet need to be stateside. Watched a few tutorials on accessing a home IP address with two GLiNet routers and set that up at a family member’s house before leaving. Worked well at home, and worked well from abroad for the first two months.

All of a sudden about a week ago after a power cut (we have those frequently in my current location) I wasn’t able to connect WireGuard. Kept trying for several days and I get the same error messages repeated in my log:

Thu Mar 19 10:58:59 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Thu Mar 19 10:58:59 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Thu Mar 19 10:58:59 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Thu Mar 19 11:00:16 2026 daemon.info dnsmasq[15416]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Thu Mar 19 11:00:17 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Thu Mar 19 11:00:18 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Thu Mar 19 11:26:57 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Thu Mar 19 11:26:58 2026 daemon.warn dnsmasq[32232]: no servers found in /tmp/resolv.conf.d/resolv.conf.wgclient1, will retry
Thu Mar 19 11:26:58 2026 daemon.info dnsmasq[32232]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Thu Mar 19 11:26:58 2026 daemon.info dnsmasq[32231]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Thu Mar 19 11:28:47 2026 user.notice wireguard-debug: USER=root ifname=wgclient1 ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Mar 19 11:28:50 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Thu Mar 19 11:28:50 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Thu Mar 19 11:28:50 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()

I used TeamViewer to access the other router located stateside and it’s connected to the internet with no issues. When I look at the log on that side, I see:

Sun Mar 29 14:12:14 2026 daemon.notice netifd: Network device 'wgserver' link is down
Sun Mar 29 14:12:15 2026 user.notice firewall: Reloading firewall due to ifdown of wgserver ()
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Section @zone[1] (wan) cannot resolve device of network 'wan6'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Section @zone[2] (guest) cannot resolve device of network 'guest'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Option 'wgserver'.masq6 is unknown
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Section 'wgserver_drop_leaked_dns' refers to not existing zone 'wgserver'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Section 'ovpnserver_drop_leaked_dns' refers to not existing zone 'ovpnserver'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231): Warning: Section @zone[2] (guest) has no device, network, subnet or extra options
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):  * Clearing IPv4 filter table
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):  * Clearing IPv4 nat table
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):  * Clearing IPv4 mangle table
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):  * Clearing IPv4 raw table
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):  * Populating IPv4 filter table
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-DHCP-Renew'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-IGMP'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-IPSec-ESP'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-ISAKMP'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-DHCP'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'Allow-DNS'
Sun Mar 29 14:12:15 2026 daemon.notice netifd: wgserver (12231):    * Rule 'lan_drop_leaked_dns'

I’m obviously a beginner at networking. Is it possible to diagnose the problem from these logs? I’m mostly surprised that it stopped working abruptly after it had been perfect for about 10 weeks. On my end the only time I really do anything is if/when there’s a power cut I press the connect button, and it’s always worked perfectly. On the other end there’s never any power cut; my family hasn’t changed ISP or hardware, everything is the same. And the router itself is connected to the internet without any problem.

Let me know what other info I can provide.

Thanks for your help

2

Hi

Based on the logs, it appears that the connection between the client and the server is being interrupted.

Could you follow the guide below to connect both devices to GoodCloud and share them with us so we can assist with remote troubleshooting?

Kindly note to send us the MAC address and the router password via private message so we can access it

image
image632×233 19.1 KB

4

Thank you for sharing the device.

However, we noticed that remote access on the MT3000 appears to have an issue, which is preventing us from checking it.

Could you export the logs and send them to us via private message so we can review its status?

image
image1430×911 87 KB

5

Thank you for providing the logs.

We noticed that the WAN interface on the MT3000 appears to be having issues—it is repeatedly restarting and flooding the logs.

Wed Apr  1 16:14:47 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:15:46 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online
Wed Apr  1 16:15:49 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:15:52 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online
Wed Apr  1 16:16:01 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:16:35 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online
Wed Apr  1 16:16:38 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:16:44 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online
Wed Apr  1 16:16:47 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:16:50 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online
Wed Apr  1 16:17:02 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status offline
Wed Apr  1 16:17:45 2026 daemon.info gl-repeater[2613]: (repeater.lua:1741) interface wan status online

This may be the root cause of the recent problems (e.g., WireGuard Server not working and GoodCloud being inaccessible remotely).

Could you check if someone else has physical access to the device and ask them to unplug the WAN cable and plug it back in securely?

Alternatively, since you currently have a repeater available, you could try disabling the WAN interface under LuCI → Network → Interfaces and use the repeater connection instead to see if this resolved the issue.

image
image1073×574 43 KB

6

Would it be possible to just unplug the WAN cable for now since the repeater already seems to be working and see if that does the trick? Sorry just trying to simplify the process as each time I connect to the router remotely I have to ask an elderly family member to connect with me via TeamViewer :sweat_smile: .

7

Yes, this should help resolve the GoodCloud remote access issues caused by network instability.

However, we noticed that the MT3000 only has a private address (10.0.0.0/24). We’re not certain whether, for the WireGuard server, you may need to adjust the port forwarding on the ISP router to forward traffic to the address obtained via the repeater, rather than the original WAN address.

8

OK WAN cable unplugged

9

We tried accessing the MT3000 via GoodCloud again, but it still failed, so there may be other factors contributing to the issue.

We’d like to see if we can arrange a remote session via TeamViewer or AnyDesk to avoid repeatedly bothering your family and to help move things forward more efficiently.

Our availability is 9:30–12:30 and 14:30–18:30 (UTC+8) on weekdays (please note we will be on a public holiday from 4/6 to 4/7).
Please let us know if this works for you and your availability.

10

I’m sorry but with the time zone difference it just won’t work. router is located in UTC-4

Would it be at all possible to try tomorrow at 19:00 (UTC+8)?

11

Do you mean 19:00 (UTC+8) on April 9?
We can try to arrange that.

However, considering it may already be late at your side, you might miss this message. If it works better for you, we can schedule it for 19:00 (UTC+8) on Friday, April 10 instead.

Please follow the guide below to set up AnyDesk, and send us the remote access details via private message at the scheduled time.
We will wait for 15 minutes—if we don’t hear from you within that window, we may need to reschedule.

image
image632×233 19.1 KB

12

yes, today 9 April at 19:00 UTC+8 (roughly 100 mins from now).

I will send the remote access details as soon as I have them.

Thanks

1 Like
13

The issue has been resolved. When examining the port forwarding setup via the ISP, I noticed the port number listed was simply ‘‘1’’ and not the number assigned to my machine. I have no idea how this change happened. Will suggested it could have been a configuration adjustment done by the ISP on their end, perhaps through protocols such as TR-069.

In any case replacing that number with the local port from the machine resolved the problem instantly.

1 Like