On Fri, Apr 12, 2024 at 1:25 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
On Fri, Apr 12, 2024 at 1:19 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Apr 12, 2024 at 2:15 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Apr 12, 2024 at 1:50 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
fundamental steps are working. my trouble is that wg show on the one machine that is left running (I shut down the wg device on the other machine intentionally so that no wg packets cause a re-establishing of the wg tunnel) "forever" shows the old address in wg show, Was this tunnel ever active? Post
yes the tunnel as is works fine. I just want to make it more robust in case both sides both parties on their ISPs go down similarly to each other and fail to have current dyndns hostnames just yet before being able to continue receiving packets from the other side (and sending into nirvana) when both sides change ip addresses close in time.
wg show wg show latest-handshake Scratch it. The script is using $EPOCHSECONDS and it is not defined in Leap 15.5 bash. Use $(date +%s) instead
I guess i copied the most current version of that script as far as I have seen there is also a mention about epoch commit stuff at
<https://git.zx2c4.com/wireguard-tools/log/?qt=grep&q=epoch>
they did have you variation in that script before:
<https://git.zx2c4.com/wireguard-tools/commit/?id=1fd95708391088742c139010cc6b821add941dec>
thanks a great deal. will try if this brings any progress. ty.
thanks I just verified with your helps changed bash file (remove epochseconds stuff) and shut down the wg0 device on the remote machine2 and re-triggered a re-dial into the broadband provider with an ip change also updating the dynamicdns hostname of that machine. within a few minutes the other machine, whose wg0 device and service is still running, how also displays the new ip address in wg show for the endpoint address being resolved and printed and set to this new ip address. so I guess everything regarding this matter is fine now. many thanks really much to you. ty! if anyone cares, please package this dns-reresolve bash script for the wireguard package as well it seems pretty basic and somewhat? essential. thanks.