Issue with Wireguard client and Dynamic DNS

riyas · 2022-06-17T07:38:08.500Z

Hopefully, this issue with be resolved quickly. For your information, watchdog script also is not really helpful for me. As I told before, sometimes (every 2nd or 3rd reconnections), my opal is stuck with Abort status. Even if I click on Abort and connect again, it won’t go further.

riyas:

I have to delete the profile and recopy the same Wireguard client profile.

So tried the watchdog method suggested by @wcs2228, unfortunately, it was stuck in Abort status. I had to remove and recopy the same profile again.

Do you have any ETA for Firmware 4.x beta ? Apart from this issue, I really like your product. I already bought 4 devices for my family

Thanks

wcs2228 · 2022-06-17T18:12:28.191Z

Since the DNS changes regularly at 23:30, another option is to shut down the router a few minutes before and to start up the router a few minutes afterwards. This can be done with an inexpensive smart plug (e.g., I have a few TP-Link HS103 for $10-$15 each).

WireGuard should reconnect automatically on reboot and hopefully pick up the new DDNS IP address.

riyas · 2022-06-20T10:45:51.484Z

Yes, you are correct. It can be a solution. But in India, they have a regular power failure during the day. They have a power backup system but the modem will lose the connection for 30 seconds. And after 30 seconds, the IP address is changed.

Unfortunately, the best solution for me would be the fix promised by the R&D team. They told me that the ETA is around 10 days. So I am waiting

Thanks again for your help.

Barfoo · 2022-09-03T15:11:48.665Z

Watchdog seems to not work with latest stable. An iOS peer with persistent keepalive config fails to connect. Running the code in CLI gives:
root@GL-AX1800:~# /usr/bin/wireguard_watchdog jsonfilter: unrecognized option: a

Not even a full
/etc/init.d/network restart
works.
I have to power off and on the router, then stop and start the Wireguard server from the glinet UI (not LUCI).
I am behind NAT with DDNS and no issues besides this one.

funfun · 2022-09-11T15:14:39.738Z

Find yourself a copy of reresolve-dns from wireguard-tools and run it every handful of minutes in the Opal. It should fix your problems. Do not wait any longer.

@Barfoo, I believe iOS and persistent keepalive aren’t relevant for @riyas

Barfoo · 2022-09-12T05:52:21.803Z

Hi, do you know where I can find a version of reresolve-dns that works on openwrt? I did found one for Linux
Here
which returns
shopt not found
And I did not find a way to install shopt on openwrt

funfun · 2022-09-12T07:06:54.341Z

The original reresolve-dns is a bash script. I’ve no idea if you can fit bash in the Opal. If you cannot, try to use this openwrt/wireguard_watchdog at master · openwrt/openwrt · GitHub . @alzhao said it doesn’t work and I do remember having to tweak it for it to work in my Beryl, but that was a while ago.

It is anyway pretty straightforward if you know a bit of scripting: check all endpoints that in the configuration are not an IP address and periodically re-resolve them if the last handshake was too long ago (e.g. a minute or two).

Barfoo · 2022-09-12T15:14:32.442Z

Maybe I am a bit naive in thinking Gl-inet could provide a working version since they advertise their products working with Wireguard and ddns at the same time
I cannot write it myself - but I confirm watchdog is not working on glinet, as I wrote in my first post on this thread - while it is reported working on other forums of openwrt.
So maybe the most elegant solution would be for glinet to build something that “makes it work” and ship it with the tools package - so we will be sure to survive upgrades, and work with “standard” Wireguard tools scripts, especially since the new functions of Wireguard that will ship with the next release…

funfun · 2022-09-12T15:20:14.049Z

Yeah, they already acknowledged it has some bugs in 3.x and 4.x will be much better. I was just trying to help you out

wireguard_watchdog should take relatively little to adapt (it is just because Gl-inet implemented Wireguard differently than OpenWRT), but unfortunately I do not have a 3.x version at the moment, so I cannot help you much more…

gb177 · 2022-10-01T03:29:00.708Z

My experience (with 3.215) on a mango router is that wireguard_watchdog doesn’t work. The ubus command in it doesn’t return anything.

The router at that point (when the wireguard connection is down) is unable to even resolve DNS names - presumably since the DNS server at 127.0.0.1 expects to use the tunnel.

Not even manually running wg set wg0 peer ... with the current IP address of the other side works.

Powercycling, or aborting and reconnecting through the web interface works - could anybody share how to find out quickly what commands I need to run in a cronjob to achieve the same effect of abort+reconnecting?

wcs2228 · 2022-10-06T23:16:15.823Z

I have not personally tested this, but you can try running the following in cron:

/etc/init.d/wireguard stop
sleep 5
/etc/init.d/wireguard start

riyas · 2022-11-27T18:29:19.490Z

Hi,

As I couldn’t wait firmware 4.x for Opal, I bought a new Slate AX with version 4.1. But unfortunately the issue is still there even with version 4.1. Do you have any update regarding this bug ?

alzhao · 2022-11-28T01:46:25.940Z

Do you mean when ddns changes IP address, wiregaurd does not reconnect?

riyas · 2022-11-28T08:37:08.558Z

Yes, the issue was there with Opal in version 3.x. You told me that the version 4 is not impacted. So bought a new Slate AXT1800 in version 4.1.0. But if the ip address change at remote server, wireguard doesn’t work anymore. It’s in Abort status.

alzhao · 2022-11-28T10:32:39.661Z

Yes. I remember.

I will check and come back.

hansome · 2022-12-06T04:13:46.385Z

Hi, could you show the screenshot with Abort status in version 4.1.0. also export log please. @riyas
I tested when the server domain change ip, after awhile of the following picture status, it will finally get connected.

image1022×493 15.6 KB

riyas · 2022-12-06T10:23:42.075Z

Finally, the workaround /usr/bin/wireguard_watchdog works with version 4.1.0. It wasn’t working in version 3.1.2.

So with version 4.1.0 it’s working.

hansome · 2022-12-06T10:48:01.881Z

Oh, I don’t use wireguard_watchdog on axt1800 4.1.0 release, and it will reconnect successfully after the server update IP.

riyas · 2022-12-06T11:13:11.415Z

Unfortunately, it wasn’t working for me after waiting more than an hour. Had to disconnect and reconnect again. With wireguard_watchdog, it works straight away

WizMeister · 2024-07-30T07:17:34.895Z

Looks like adding /usr/bin/wireguard_watchdog cron job doesn't work on 4.6.2 (Flint 2)