hello,
i set up wireguard client but when i try to connect i am getting following error
kern.info kernel: [54847.403001] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT
any idea?
As mentioned many places, WireGuard’s logging sucks. This is basically the client’s way of saying “something is wrong” without telling you anything about what that might be.
I would double check all of your settings to make sure they are correct. If they are, we’ll need some additional information (e.g., what are you trying to connect to, etc.) to actually be able to provide any useful help.
the config is identical as on my laptop;
so where i can find more debug info?
using ssh to a1300?
it got connected afterwards disconnected…
Tue Dec 6 12:11:15 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Tue Dec 6 12:11:15 2022 daemon.notice netifd: Interface 'wgclient' has lost the connection
Tue Dec 6 12:11:15 2022 daemon.notice netifd: Network device 'wgclient' link is down
Tue Dec 6 12:11:16 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Tue Dec 6 12:11:17 2022 daemon.notice netifd: wgclient (12668): udhcpc: started, v1.33.2
Tue Dec 6 12:11:17 2022 daemon.notice netifd: wgclient (12668): udhcpc: sending discover
Tue Dec 6 12:11:19 2022 daemon.notice netifd: wgclient (12668): udhcpc: no lease, failing
Tue Dec 6 12:11:19 2022 daemon.notice netifd: wgclient (12668): udhcpc: started, v1.33.2
Tue Dec 6 12:11:20 2022 daemon.notice netifd: wgclient (12668): udhcpc: sending discover
Tue Dec 6 12:11:20 2022 daemon.notice netifd: Interface 'wgclient' is now down
Tue Dec 6 12:11:20 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Tue Dec 6 12:11:26 2022 kern.info kernel: [56162.627521] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT
Tue Dec 6 12:11:26 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/
and now its constantly failing with the error from my 1. post.
Pretty sure connection messages look different than that. I’d say it never connected.
You can always use wg show to start debugging.
Some providers have other instructions, but as someone who self hosts I don’t know what those might be.
i set up my wireguard server on other openwrt router and all clietns can connect to it.
only a1300 cant . seems that device is like for kids … not for normal use…
The only times I’ve had a problem connecting to a real Linux WireGuard server were errors when I messed something up in the config file. Wrong port, wrong ip, not putting a /32 on the end of the address, etc.
Post your config with the keys redacted.
config is copypaster from working client.
[Interface]
Address = 192.168.9.4/32
ListenPort = 30464
PrivateKey = xxx
DNS = 10.0.1.1
[Peer]
AllowedIPs = 0.0.0.0/0
Endpoint = xxx.dynu.com:51820
PersistentKeepalive = 25
PublicKey = xxxx
PresharedKey = xxx
Are you trying to connect from the LAN side of that other router?
Also the guest wifi for glinet products is in the 192.168.9.0/24 range. You’ll probably need to change that. You’re probably getting tangled up in those firewall rules.
this is not for debugging …
this is not for debugging …
Ok, you seem to be more than capable to do this on your own then. Best of luck.
(Though you might at least consider my post above about the overlapping ip range, which is almost certainly your problem)
lol kiddo
no i am not saying i am more then capable but this is nothing to do with debugging
and again NO
i changed wireguard server ip to 192.168.55.1/
and clients to 192.168.55.3
and it doesnt work so no its not the issue.
there is something other BROKEN
/usr/bin:/sbin:/bin PWD=/
Tue Dec 6 13:09:51 2022 daemon.notice netifd: wgclient (7757): udhcpc: started, v1.33.2
Tue Dec 6 13:09:51 2022 daemon.notice netifd: wgclient (7757): udhcpc: sending discover
Tue Dec 6 13:09:53 2022 daemon.notice netifd: wgclient (7757): udhcpc: no lease, failing
Tue Dec 6 13:09:54 2022 daemon.notice netifd: wgclient (7757): udhcpc: started, v1.33.2
Tue Dec 6 13:09:54 2022 daemon.notice netifd: wgclient (7757): udhcpc: sending discover
The DNS/dhcp client? It’s a the same compiled binary man, same across all OpenWRT devices. It’s not a bug.
Send it back, you’re clearly not going to be happy.
the ip address for wireguard client is set fixed;
there is nothing to do with dhcp.
with kiddish crap tool noone will be happy.
Unlike the hot mess that is the 6000 series, the 4000 series is actually quite stable. If you think there’s a problem with the GLI front end, like I said, put a stock version of Open WRT on it.
But everybody’s pulling from the same wire guard code. I can assure you that GLI is not doing anything different. The problem is in the configuration, not the code.
Like I said, you obviously know more than the rest of us here, and you’re not going to be happy with the device. Send it back. I’m not particularly interested in helping you debug this problem further. Someone else may be.