On 12/5/16 11:52 AM, David Miller wrote:
From: Erik Nordmark <nordm...@arista.com>
Date: Sat, 3 Dec 2016 20:57:09 -0800
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 <nordm...@arista.com>
Signed-off-by: Bob Gilligan <gilli...@arista.com>
Applied to net-next, thanks.
Thanks, especially for moving it from net to net-next.
I guess I don't fully understand what is considered a bug fix for net as
opposed to new stuff for net-next. Is the former mostly for regressions
and serious bugs? This was a fix for a bug that's been there since the
beginning of IPv6 time AFAICT.
Erik
