Hi Broderick, this already happens!!
If you have a wireguard server on your Router and WAN1 is the primary, and it goes down the router switches to WAN2, the clients connecting to your WG server will lose connectivity and will try to reconnect and when the WANIP for the router becomes the second ISP IP, the client will reconnect ( assumes your domain name URL or IP cloud also adjusts to the new WANIP aak the endpoint address becomes relevant after some period of down time). Typically this could easily be 30 seconds to a minute and a half.......... not sure exactly.
So you will in effect get reconnected and also when WAN1 comes back up. So need to do anything its built-in.
Assuming that your talking about remote users to Wireguard and not router to router wireguard?
Now you could add a second wireguard interface just to use for WAN2 and thus you have always have two endpoints one for each WAN and thus if one goes down it would take you seconds to switch to the alternate.
If you have a wireguard server on your Router and WAN1 is the primary, and it goes down the router switches to WAN2, the clients connecting to your WG server will lose connectivity and will try to reconnect and when the WANIP for the router becomes the second ISP IP, the client will reconnect ( assumes your domain name URL or IP cloud also adjusts to the new WANIP aak the endpoint address becomes relevant after some period of down time). Typically this could easily be 30 seconds to a minute and a half.......... not sure exactly.
So you will in effect get reconnected and also when WAN1 comes back up. So need to do anything its built-in.
Assuming that your talking about remote users to Wireguard and not router to router wireguard?
Now you could add a second wireguard interface just to use for WAN2 and thus you have always have two endpoints one for each WAN and thus if one goes down it would take you seconds to switch to the alternate.
Statistics: Posted by anav — Mon Dec 04, 2023 8:56 pm
