Should I expect faster recovery after one side goes down
Bruno Wolff III
bruno at wolff.to
Fri Dec 1 18:02:39 CET 2017
On Fri, Dec 01, 2017 at 09:43:19 +0100,
Baptiste Jonglez <baptiste at bitsofnetworks.org> wrote:
>It sounds like one of these situations where persistent keepalives would
>be useful, doesn't it?
It is definitely useful as the laptop is expected to be behind NAT, but it
doesn't help with the rebooting the router breaking historical source
NAT (on my local network) while the other end remembers where it last got a
packet from. The solution below dealt with that.
>> I found a way to make it work more automatically. The reason the port was
>> getting reassigned was because the original connection packet was being
>> tracked and was conflicting with the source nat mapping even though in
>> reallity the connection was the same. By putting in CT --notrack rules I was
>> able to block that traking and without the conflict the port doesn't get
>> remapped. I don't need tracking or the original connection for my firewall
>> rules so this should be OK. On testing it seems to work as expected. Now
>> when I reboot my router, my laptop reconnects and the wireguard tunnel works
>> without having to restart it.
More information about the WireGuard