I've been using wireguard for a point-to-point connection for over 1 year. Twice I've had an issue where it stopped working and didn't restart on it's own. Fortunately I have a backup openvpn connection. It appear that the local router was rebooted and for some reason failed it's dyndns update, which caused both the wireguard and openvpn connection to stop working, because the remote (which is initiating both of these vpn connections) can't find the correct public IP to connect. Manually fixing the dyndns, I found that after some time (the next morning) the openvpn connection was working. But not wireguard. Using openvpn I had to restart wireguard on the remote using systemctl restart wg-quick@wg0. This makes the second time that wireguard has gotten stuck and failed to repair itself. Good thing I still have openvpn as a backup. Any thoughts? Thanks, Neal -- Those who don't understand recursion are doomed to repeat it _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
