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 abdab69c for ; Wed, 29 Nov 2017 10:59:02 +0000 (UTC) Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com [209.85.128.172]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id ce31570c for ; Wed, 29 Nov 2017 10:59:02 +0000 (UTC) Received: by mail-wr0-f172.google.com with SMTP id z18so2991764wrb.8 for ; Wed, 29 Nov 2017 03:05:01 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: d tbsky Date: Wed, 29 Nov 2017 19:05:00 +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-23 7:35 GMT+08:00 Jason A. Donenfeld : > On Tue, Nov 21, 2017 at 3:35 PM, d tbsky wrote: >> thanks for the quick reply. my wireguard configuration is in the >> previous mail, so I think the linux firewall part is what you want. > > Right. So if you can give me minimal instructions on how to set up a > box that exhibits the buggy behavior you're seeing, I can try to fix > it. > > Jason Hi jason: are you still interested with the problem? today I try to use multi-home client to connect server. and I found not only server, but client suffered. the problem seems at rhel linux kernel side, but I am not sure. since wireguard was the only victim I met. I can create a virtual machine with ssh access if you want to test these strange problems. btw, is it possible that wireguard bind to specific ip in the future? I think it will solve all the problems, but maybe you have technical concerns. thanks a lot for your help. Regards, tbskyd