From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] iplink_vxlan: take into account preferred_family creating vxlan device
Date: Fri, 21 Sep 2018 18:35:35 +0200 [thread overview]
Message-ID: <20180921163534.GC15752@localhost.localdomain> (raw)
In-Reply-To: <20180921085805.7ee078e8@xeon-e3>
> On Fri, 21 Sep 2018 15:34:25 +0200
> Lorenzo Bianconi <lorenzo.bianconi@redhat.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@redhat.com>
>
> This patch was already in the queue. Is this a new version (if so please mark it as v2).
Hi Stephen,
yes, this is a v2. I missed v2 in the subject and changes respect to v1
(I have just modified the commit log actually). Please drop v1 and sorry for
the noise.
Regards,
Lorenzo
>
next prev parent reply other threads:[~2018-09-21 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1537536423.git.lorenzo.bianconi@redhat.com>
2018-09-21 13:34 ` [PATCH iproute2] iplink_vxlan: take into account preferred_family creating vxlan device Lorenzo Bianconi
2018-09-21 15:58 ` Stephen Hemminger
2018-09-21 16:35 ` Lorenzo Bianconi [this message]
2018-09-25 8:12 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180921163534.GC15752@localhost.localdomain \
--to=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.