From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: yoshfuji@linux-ipv6.org, idosch@mellanox.com,
roopa@cumulusnetworks.com, David Ahern <dsahern@gmail.com>
Subject: [PATCH v2 net-next 0/3] net/ipv6: Add support for ONLINK flag
Date: Thu, 25 Jan 2018 16:55:06 -0800 [thread overview]
Message-ID: <20180126005509.14318-1-dsahern@gmail.com> (raw)
Add support for RTNH_F_ONLINK with ipv6 routes.
First patch moves existing gateway validation into helper. The onlink
flag requires a different set of checks and the existing validation
makes ip6_route_info_create long enough.
Second patch makes the table id and lookup flag an option to
ip6_nh_lookup_table. onlink check needs to verify the gateway without
the RT6_LOOKUP_F_IFACE flag and PBR with VRF means the table id can
vary between the table the route is inserted and the VRF the egress
device is enslaved to.
Third patch adds support for RTNH_F_ONLINK.
I have a set of test cases in a format based on the framework Ido and
Jiri are working on. Once that goes in I will adapt the script and
submit.
v2
- removed table id check. Too constraining for PBR with VRF use cases
David Ahern (3):
net/ipv6: Move gateway validation into helper
net/ipv6: Add flags and table id to ip6_nh_lookup_table
net/ipv6: Add support for onlink flag
net/ipv6/route.c | 140 ++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 103 insertions(+), 37 deletions(-)
--
2.11.0
next reply other threads:[~2018-01-26 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 0:55 David Ahern [this message]
2018-01-26 0:55 ` [PATCH v2 net-next 1/3] net/ipv6: Move gateway validation into helper David Ahern
2018-01-26 0:55 ` [PATCH v2 net-next 2/3] net/ipv6: Add flags and table id to ip6_nh_lookup_table David Ahern
2018-01-26 0:55 ` [PATCH v2 net-next 3/3] net/ipv6: Add support for onlink flag David Ahern
2018-01-26 15:19 ` [PATCH v2 net-next 0/3] net/ipv6: Add support for ONLINK flag 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=20180126005509.14318-1-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=yoshfuji@linux-ipv6.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).