# 4.x Wireguard REKEY-TIMEOUT troubleshooting

**URL:** <https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814>\
**Category:** Router\
**Tags:** Featured\
**Created:** [December 14, 2022, 9:46am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814 "2022-12-14T09:46:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\
**Post date:** [January 1, 2023, 2:22pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/6 "2023-01-01T14:22:07Z")

</div>

Update one case:

The ISP blocked incoming UDP traffic on the modem.

Even you set up port forward it does not work.

> [@Wireguard client doesn't work on GL-MT2500A](https://forum.gl-inet.com/t/wireguard-client-doesnt-work-on-gl-mt2500a/26044):
>
> Hi, I’m using 2 GL-MT2500A routers, the first one is my wireguard server and the second one is my wireguard client. Everything worked fine during a month. 3 days ago the wireguard client stopped to connect and show this error: Sat Dec 24 19:43:12 2022 daemon.notice netifd: Interface ‘wgclient’ is setting up now Sat Dec 24 19:43:12 2022 daemon.err tailscaled[6499]: 2022/12/24 18:43:12 LinkChange: major, rebinding. New state: interfaces.State{defaultRoute=eth0 ifs={br-lan:[192.168.8.1/24] eth0:…

---

_[View the full topic](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814)._