Something happened with wireguard handshake counter.
It generate negative values and only count to 1 minutes.
Then your system time might be off
1 Like
System time is right.
Negative time difference disproves it.
Add both wg tunnel ends as ntp noselect peers to record time skews
What is the output of date?
root@Defcon:~# date
Sat Jan 31 22:29:19 CET 2026
Seems right. What version of OpenWrt?
ubus call system board
root@Defcon:~# ubus call system board
{
"kernel": "6.6.119",
"hostname": "Defcon",
"system": "ARMv8 Processor rev 4",
"model": "GL.iNet GL-MT6000",
"board_name": "glinet,gl-mt6000",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.5",
"revision": "r29087-d9c5716d1d",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.5 r29087-d9c5716d1d",
"builddate": "1766005702"
}
}
It could be because the clock at the other end is wrong, and ahead of the actual time.
Wireguard doesn't use certificates that expire at a definite time, but I think the two system times have to be close for a successful handshake.
1 Like
