summaryrefslogtreecommitdiffstats
path: root/net/ipv6/route.c
diff options
context:
space:
mode:
authorErik Nordmark <nordmark@arista.com>2016-12-03 20:57:09 -0800
committerDavid S. Miller <davem@davemloft.net>2016-12-05 14:52:05 -0500
commit96d5822c1d812ed30da035795a4408f43fe533f3 (patch)
tree16ef76dfd501f82c59242dde32193fd9f02113e7 /net/ipv6/route.c
parent3c839744b33782b930c5c61df35511ede5e5a574 (diff)
downloadop-kernel-dev-96d5822c1d812ed30da035795a4408f43fe533f3.zip
op-kernel-dev-96d5822c1d812ed30da035795a4408f43fe533f3.tar.gz
ipv6: Allow IPv4-mapped address as next-hop
Made kernel accept IPv6 routes with IPv4-mapped address as next-hop. It is possible to configure IP interfaces with IPv4-mapped addresses, and one can add IPv6 routes for IPv4-mapped destinations/prefixes, yet prior to this fix the kernel returned an EINVAL when attempting to add an IPv6 route with an IPv4-mapped address as a nexthop/gateway. RFC 4798 (a proposed standard RFC) uses IPv4-mapped addresses as nexthops, thus in order to support that type of address configuration the kernel needs to allow IPv4-mapped addresses as nexthops. Signed-off-by: Erik Nordmark <nordmark@arista.com> Signed-off-by: Bob Gilligan <gilligan@arista.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/route.c')
-rw-r--r--net/ipv6/route.c5
1 files changed, 4 insertions, 1 deletions
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index aac7818..2413a06 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -2000,8 +2000,11 @@ static struct rt6_info *ip6_route_info_create(struct fib6_config *cfg)
It is very good, but in some (rare!) circumstances
(SIT, PtP, NBMA NOARP links) it is handy to allow
some exceptions. --ANK
+ We allow IPv4-mapped nexthops to support RFC4798-type
+ addressing
*/
- if (!(gwa_type & IPV6_ADDR_UNICAST))
+ if (!(gwa_type & (IPV6_ADDR_UNICAST |
+ IPV6_ADDR_MAPPED)))
goto out;
if (cfg->fc_table) {
OpenPOWER on IntegriCloud