netdev - Re: [PATCH iproute2] iplink_vxlan: take into account preferred

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180925101250.47992dec@shemminger-XPS-13-9360>
Date:   Tue, 25 Sep 2018 10:12:50 +0200
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Lorenzo Bianconi <lorenzo.bianconi@...hat.com>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] iplink_vxlan: take into account
 preferred_family creating vxlan device

On Fri, 21 Sep 2018 15:34:25 +0200
Lorenzo Bianconi <lorenzo.bianconi@...hat.com> wrote:

> Take into account the configured preferred_family if neither saddr or
> daddr are provided since otherwise vxlan kernel module will use IPv4 as
> default remote inet family neglecting the one provided by userspace.
> This behaviour was originally in commit 97d564b90ccb ("vxlan: use
> preferred address family when neither group or remote is specified").
> The issue can be triggered with the following reproducer:
> 
> $ip -6 link add vxlan1 type vxlan id 42 dev enp0s2 \
>      proxy nolearning l2miss l3miss
> $bridge fdb add 46:47:1f:a7:1c:25 dev vxlan1 dst 2000::2
> RTNETLINK answers: Address family not supported by protocol
> 
> Fixes: 1e9b8072de2c ("iplink_vxlan: Get rid of inet_get_addr()")
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@...hat.com>

Applied, thanks.