From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: bruno@wolff.to Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 5b7722a2 for ; Tue, 28 Nov 2017 08:38:00 +0000 (UTC) Received: from wolff.to (wolff.to [98.103.208.27]) by krantz.zx2c4.com (ZX2C4 Mail Server) with SMTP id bbd57613 for ; Tue, 28 Nov 2017 08:38:00 +0000 (UTC) Date: Tue, 28 Nov 2017 02:42:37 -0600 From: Bruno Wolff III To: "Jason A. Donenfeld" Subject: Re: Should I expect faster recovery after one side goes down Message-ID: <20171128084237.GA12292@wolff.to> References: <20171127094931.GA3104@wolff.to> <20171127134914.GA9392@wolff.to> <20171127173354.GA17685@wolff.to> <20171127182558.GA19220@wolff.to> <20171128061306.GA7842@wolff.to> <20171128064413.GA9218@wolff.to> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed In-Reply-To: <20171128064413.GA9218@wolff.to> Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Nov 28, 2017 at 00:44:13 -0600, Bruno Wolff III wrote: > >I think the correct fix is to know if I reboot the router for testing >something, I need to also restart wireguard to make sure it is sending >data to the expected port. This isn't going to be an issue in normal >operation. 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.