Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753485AbcKMBAp (ORCPT ); Sat, 12 Nov 2016 20:00:45 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:57112 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752084AbcKMBAn (ORCPT ); Sat, 12 Nov 2016 20:00:43 -0500 MIME-Version: 1.0 In-Reply-To: <1478998272.2299343.785875225.19237693@webmail.messagingengine.com> References: <31e050e2-0499-a77e-f698-86e58ad2fa6b@cumulusnetworks.com> <0dbf5deb-bffb-4878-a268-1adb17c47676@cumulusnetworks.com> <1478998272.2299343.785875225.19237693@webmail.messagingengine.com> From: "Jason A. Donenfeld" Date: Sun, 13 Nov 2016 02:00:38 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Source address fib invalidation on IPv6 To: Hannes Frederic Sowa Cc: David Ahern , Netdev , WireGuard mailing list , LKML , YOSHIFUJI Hideaki Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 574 Lines: 16 Hi Hannes, On Sun, Nov 13, 2016 at 1:51 AM, Hannes Frederic Sowa wrote: > You probably need some combination of ipv6_chk_addr and/or > ipv6_check_addr_and_flags (where dev can also be NULL). Be careful if a > IFA_HOST or IFA_LINK address switches from one interface to another. I can confirm this trick works beautifully: https://git.zx2c4.com/WireGuard/commit/?id=eb65810fc6350c50b42abedd1291b12337d3dc3d I'll see if I can fold this into the routing function so that it behaves the same as v4, unless David gets there first. Regards, Jason