Flint Stuck in endless loop on Wireguard start

gor1kgor1k · 2022-11-29T10:28:18.644Z

Same issue here - works on the laptop itself, but can’t connect my router.
Tue Nov 29 13:26:32 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Tue Nov 29 13:26:37 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/

Serd · 2022-12-12T20:50:25.314Z

This is my endless loop

ser.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/

I have two wireguard VPN servers (created with pivpn) on two different raspberrys, but after updating to the last Flint version I can’t connect to them, but they are working as I can connect using MV1000 and using the android wireguard client

Any ideas ? Do you need any extra info?

K3rn3l_Ku5h · 2022-12-12T20:54:45.255Z

Are you using GUI of LuCi for setup?

Serd · 2022-12-13T07:23:12.733Z

I used GUI for the setup

alzhao · 2022-12-13T09:38:11.965Z

It does not connect at all, or it connect and break?

If it is the first case, may need to verify the config once again on your phone etc.

If you can, send me one config in private message.

Serd · 2022-12-13T20:13:34.546Z

it doesn’t connect
it works in the MV1000 and in the phone

blindman · 2023-01-14T03:50:23.660Z

I am getting the same problem

tech333 · 2023-01-16T01:16:43.982Z

Same. Did anyone figure this out? @alzhao @Serd

K3rn3l_Ku5h · 2023-01-16T15:28:54.245Z

Update Uboot
Do a clean install to 4.x using Uboot
Setup.

Most of the issues is caused by keeping settings

Back ups that are created in LuCi seem to work (don’t reuse a backup config file generated in 3.x

tech333 · 2023-01-16T21:57:23.513Z

Thanks for replying. Looks like it was a config file misconfiguration with the public key. I got it working, but now I keep getting this in the log, is it normal?

Mon Jan 16 16:45:47 2023 kern.info kernel: [ 1147.694386] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED
Mon Jan 16 16:45:47 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Jan 16 16:47:47 2023 kern.info kernel: [ 1268.161091] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED
Mon Jan 16 16:47:47 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Jan 16 16:49:47 2023 kern.info kernel: [ 1388.646300] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED
Mon Jan 16 16:49:48 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Jan 16 16:51:48 2023 kern.info kernel: [ 1509.035397] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=KEYPAIR-CREATED
Mon Jan 16 16:51:48 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/

K3rn3l_Ku5h · 2023-01-17T01:18:51.664Z

Who is the VPN provider? alzhao I think did mention something about certain VPN that the keypair did not work. Also it might be a issue in you vpn config file.

Not sure if this is related:

Slate AX (GL-AXT1800) Wireguard Issue (REKEY-TIMEOUT) Technical Support for Routers

Today I worked with @hectorricardo to solve the problem. Several problems are identified. The wireguard config from Starvpn use domain name as endpoint. The domain resolves to several IP addresses. Different network will resolve to different IP address. Some IP addresses does not work. When hard core to certain IP address, it works OK. So this is definately a problem of Startvpn. This is verified on windows pc as well. Two bugs identified on our firmware: (a) The firmware does not work well wi…

tech333 · 2023-01-17T04:22:09.639Z

It is my own wireguard server router on openwrt 23.03.03 at a different location setup using the wireguard server setup wiki on openwrt. The DNS is the main router IP address, which the openwrt server router is behind. Here is my config file for the client:

[Interface]
Address = 192.168.9.2/24
ListenPort = 51820
PrivateKey = yGzJjxxxxxxxxxxxxxxxxxxxx
DNS = 192.168.4.1

[Peer]
AllowedIPs = 0.0.0.0/0
Endpoint = exaxxxx.duckdns.org:51820
PersistentKeepalive = 25
PublicKey = Eorq+jDgkxxxxxxxxxxxxxxxxxxx
PresharedKey = es79xpyxxxxxxxxxxxxxxxx

alzhao · 2023-01-17T07:13:56.798Z

Pls check if your ddns resolves to the same IP everytime.

I also observe that your used 192.168.9.x and 192.168.4.x subnet. Pls make sure these are valid.

If you cannot make it work at all, it may be your server side set up.

Correia · 2023-03-03T20:30:20.157Z

I have the same issue. It stays in a loop trying to connect.

In my GL-MT300N-V2 everything works fine.

I just upgraded to a GL-MT2500A and I cannot connect to my Wireguard VPN.

I am using VPN Unlimited as a VPN provider.

And I have an additional issue that I do not know if it is related…

When I stop my failed wireguard connection, I lose connection to the internet. I need to restart the router in order to get connection to the internet.

Correia · 2023-03-03T20:43:53.161Z

Got it working! And found my problem…

When adding Manual configuration, it is ignoring Peer PresharedKey. I add in Item Mode and got it working.

alzhao · 2023-03-06T10:27:36.625Z

Correia:

When adding Manual configuration, it is ignoring Peer PresharedKey.

I remember this bug. It should have been fixed in latest firmware.

buendia · 2023-03-24T15:08:26.585Z

Up^ I have the same “issue” in my logs @alzhao is it OK?

alzhao · 2023-03-25T02:58:57.232Z

Log does not show the reason. But the latest snapshot should have fixed everything.

MELIM · 2023-03-31T09:46:04.625Z

Hi
i have same issue version 4.0.3 Release 7

wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nFri Mar 31 09:32:39 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nFri Mar 31 09:32:44 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\n"

alzhao · 2023-03-31T10:38:05.454Z

MELIM:

i have same issue version 4.0.3 Release 7

Pls upgrade to latest snapshot or beta