I have a problem with wireguard Site2Site. One of the parties has a variable IP address with a DDNS service. By giving the DDNS address to the other party, the tunnel sets up, but when the address is changed, there is no communication. It looks like the address in the Endpoint field is not refreshed on the other side without disabling and enabling the interface.
Has anyone had a similar problem? Is this correct behavior?
As Msatter and Anav pointed out there are some scripts that may solve the problem although it often requires quite some knowledge och experience how to install and configure them.
I sincerely do hope that Mikrotik will solve this shortcoming in the near future so you’re not forced to use all these quick 'n dirty hacks.
There were of course no intention at all to diminish all the wonderful fabulous delightful script makers and their truly amazing marvellous heavenly scripts that solves obvious shortcomings in RoS. Thank you for your service!
The need for scripts identifies requirements that were not visualized by the coders or not approved by $$upper management.
Thus such scripts are a replacement for the notdone.
To make them elegant is indeed a skill. There will always be need for such skills but the point is that one should be able to USE such a function in a script for the ODD scenario.
For the COMMON DOG FUCK scenario, MT should have a simple automated mechanism builtin to the keep alive function (clearly if you want keep alive active, then you want the connection active) or a checkbox option to enable such a function. Accessing the function for the more complex edge cases in a script will still have its place.