ipv6: Allow IPv4-mapped address as next-hop
authorErik Nordmark <nordmark@arista.com>
Sun, 4 Dec 2016 04:57:09 +0000 (20:57 -0800)
committerDavid S. Miller <davem@davemloft.net>
Mon, 5 Dec 2016 19:52:05 +0000 (14:52 -0500)
commit96d5822c1d812ed30da035795a4408f43fe533f3
tree16ef76dfd501f82c59242dde32193fd9f02113e7
parent3c839744b33782b930c5c61df35511ede5e5a574
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>
net/ipv6/route.c