You’re using beta firmware, right? Please send me a private message with the system log.
Also please check this command output when issue happens:
wg
Sent you direct message with information
After testing and researching for so long, I think I have reproduced your same issue. The conclusion is that when the 51820 port is blocked, there will be a situation where the wireguard cannot be connected, and the interface shows that the connection is successful but actually unsuccessful.
The snapshot firmware addresses this issue by using a different port to communicate with port 51820 each time it reconnects.
If you already add the wireguard conf, and there was a previous auto-generated listen port, please remove it.
2 Likes
Sounds good. Will this solution be cascaded to all Routers on 4.x F/W e.g. the Beryl AX?
Yes, it will be applied to all 4.x FW
1 Like
@hansome
Thank you for the investigation. I will try this snapshot and let you know how it goes.
1 Like
Please generate a configuration backup(http://192.168.8.1/cgi-bin/luci/admin/system/flash) and export log(http://192.168.8.1/#/logview) , send me by PM or email to handongming@gl-inet.com
Did the fake wireguard connection happen? or only a system crash?
Sent you the files through PM.
Looks like system crash and fake wireguard connection happened. I saw exactly same symptoms as before I moved to the snapshot firmware you created.
Thank you very much. I’ll check the logs, do some tests, and get back to you asap.
1 Like