diff options
| author | Erik Nordmark <nordmark@arista.com> | 2016-12-04 07:57:09 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-12-05 22:52:05 +0300 |
| commit | 96d5822c1d812ed30da035795a4408f43fe533f3 (patch) | |
| tree | 16ef76dfd501f82c59242dde32193fd9f02113e7 /scripts/checkstack.pl | |
| parent | 3c839744b33782b930c5c61df35511ede5e5a574 (diff) | |
| download | linux-96d5822c1d812ed30da035795a4408f43fe533f3.tar.xz | |
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 'scripts/checkstack.pl')
0 files changed, 0 insertions, 0 deletions