From: David Miller <davem@davemloft.net>
To: martynas@weave.works
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] vxlan: Set flow*_dport when doing route lookups
Date: Tue, 10 Jan 2017 21:10:04 -0500 (EST) [thread overview]
Message-ID: <20170110.211004.1712612611986550798.davem@davemloft.net> (raw)
In-Reply-To: <20170110172945.24676-1-martynas@weave.works>
From: Martynas Pumputis <martynas@weave.works>
Date: Tue, 10 Jan 2017 17:29:45 +0000
> Otherwise, no xfrm policy with dport being set can be matched.
>
> Signed-off-by: Martynas Pumputis <martynas@weave.works>
And likewise you should also be adding the source port, since it is
available, to the route lookup as well.
next prev parent reply other threads:[~2017-01-11 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:29 [PATCH] vxlan: Set flow*_dport when doing route lookups Martynas Pumputis
2017-01-11 2:10 ` David Miller [this message]
2017-01-11 15:18 ` [PATCH v2] vxlan: Set ports in flow key " Martynas Pumputis
2017-01-11 21:10 ` David Miller
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=20170110.211004.1712612611986550798.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=martynas@weave.works \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).