From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tbskyd@gmail.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id f85724f2 for ; Fri, 1 Dec 2017 07:38:10 +0000 (UTC) Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 761b11de for ; Fri, 1 Dec 2017 07:38:10 +0000 (UTC) Received: by mail-wr0-f177.google.com with SMTP id z34so9053851wrz.10 for ; Thu, 30 Nov 2017 23:44:24 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20171129135124.GA29970@zx2c4.com> From: d tbsky Date: Fri, 1 Dec 2017 15:44:22 +0800 Message-ID: Subject: Re: multi-home difficulty To: "Jason A. Donenfeld" Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 2017-11-29 22:49 GMT+08:00 Jason A. Donenfeld : > On Wed, Nov 29, 2017 at 3:16 PM, d tbsky wrote: >> sorry I misunderstand you. you mean I modify the script and run >> in my environment to reveal the problem? >> ok I will try to do it. > > Take what I sent you. Run it. If it breaks, send me the output and > your kernel. If it doesn't break, mess with it until it breaks, and > then send it back to me. Hi jason: during test in netns environment, I saw something that I never saw at real world. the steps below: 1. client try connect to multi-home-server. 2. wait for conntrack session timeout both for client and server. 3. server try connect to client. server will use source ip at step1 to connect. it means at step1, wireguard not only remember client's ip address, but also remember self source ip address. even though the source address didn't show at "wg wg0" user interface. is the assumption true? I didn't see this behavior in real world. Regards, tbskyd