Wireguard needs to be restarted on dynamic DNS IP change
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello, I'm running ER605 v2 router at firmware 2.3.3, and I've noticed that the following steps do not work:
1. Enable Wireguard interface in Omada controller.
2. Router connection is dropped by ISP and reconnected to a new public WAN IP address
3. A WG peer attempts to connect to router at new public WAN IP address but it seems it's not listening.
However, if the WG interface in Omada is disabled and then re-enabled, the WG peer is immediately able to connect as expected at the new public WAN address.
It would seem as if the WG service in the router is not adapting to the new public WAN IP address, and might still be listening on the obsolete WAN IP address?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @watou
Thanks for posting in our business forum.
watou wrote
Hello, I'm running ER605 v2 router at firmware 2.3.3, and I've noticed that the following steps do not work:
1. Enable Wireguard interface in Omada controller.
2. Router connection is dropped by ISP and reconnected to a new public WAN IP address
3. A WG peer attempts to connect to router at new public WAN IP address but it seems it's not listening.
However, if the WG interface in Omada is disabled and then re-enabled, the WG peer is immediately able to connect as expected at the new public WAN address.
It would seem as if the WG service in the router is not adapting to the new public WAN IP address, and might still be listening on the obsolete WAN IP address?
Based on your description, our test team got back to me and said that they did not reproduce this issue. So, is your issue resolved?
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
I do not know why this issue disappeared and is now working properly, consistent with the observations of your test team. Some other cause must have required the Wireguard interface to be disabled and then re-enabled in order to work, because the mere changing of public WAN IP address does not now appear to be the issue.
Thank you for following up.
Kind regards,
watou
- Copy Link
- Report Inappropriate Content
Hi @watou
Thanks for posting in our business forum.
I remember that WG officials did not support renewing the IP address if it had been changed when I was learning the WG VPN.
Second, this re-enable is like the wg down and wg up which reboots the WG service so it can start to listen on the new port.
When the service is up, it does not change the WAN IP address or you may say sync the new IP because it can cause disconnection. The common practice would be down and up again.
I am not sure if this has been fixed by the WG official.
- Copy Link
- Report Inappropriate Content
Hi @watou
Thanks for posting in our business forum.
watou wrote
Hello, I'm running ER605 v2 router at firmware 2.3.3, and I've noticed that the following steps do not work:
1. Enable Wireguard interface in Omada controller.
2. Router connection is dropped by ISP and reconnected to a new public WAN IP address
3. A WG peer attempts to connect to router at new public WAN IP address but it seems it's not listening.
However, if the WG interface in Omada is disabled and then re-enabled, the WG peer is immediately able to connect as expected at the new public WAN address.
It would seem as if the WG service in the router is not adapting to the new public WAN IP address, and might still be listening on the obsolete WAN IP address?
Based on your description, our test team got back to me and said that they did not reproduce this issue. So, is your issue resolved?
- Copy Link
- Report Inappropriate Content
Hi @Clive_A
I do not know why this issue disappeared and is now working properly, consistent with the observations of your test team. Some other cause must have required the Wireguard interface to be disabled and then re-enabled in order to work, because the mere changing of public WAN IP address does not now appear to be the issue.
Thank you for following up.
Kind regards,
watou
- Copy Link
- Report Inappropriate Content
I have the same issue with my PPTP VPN. When I restart my modem (after which it gets a new WAN IP from my ISP) or when my modem gets a new IP from my ISP every morning, the remote gateway cannot connect to the PPTP VPN server with the new IP.
ER605 Router --- Modem (Dynamic Global IP) ---------- Internet ---------- ER605 Router (no global IP)
PPTP Server PPTP Client
IP Changes IP of hostname updates PPTp Client cannot connect to PPTP Server
After reboot or
at 5 o'clock
in the morning
- Copy Link
- Report Inappropriate Content
Hi @vedat
Thanks for posting in our business forum.
vedat wrote
I have the same issue with my PPTP VPN. When I restart my modem (after which it gets a new WAN IP from my ISP) or when my modem gets a new IP from my ISP every morning, the remote gateway cannot connect to the PPTP VPN server with the new IP.
ER605 Router --- Modem (Dynamic Global IP) ---------- Internet ---------- ER605 Router (no global IP)
PPTP Server PPTP Client
IP Changes IP of hostname updates PPTp Client cannot connect to PPTP Server
After reboot or
at 5 o'clock
in the morning
You are not facing the same issue as the OP who uses Wireguard VPN. Please start a new thread and I will get back to you.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1237
Replies: 5
Voters 0
No one has voted for it yet.