diff options
| author |   Erik Nordmark <nordmark@arista.com> | 2016-12-03 20:57:09 -0800 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2016-12-05 14:52:05 -0500 |
| commit | 96d5822c1d812ed30da035795a4408f43fe533f3 (patch) | |
| tree | 16ef76dfd501f82c59242dde32193fd9f02113e7 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | bpf: Preserve const register type on const OR alu ops (diff) | |
| download | linux-dev-96d5822c1d812ed30da035795a4408f43fe533f3.tar.xz linux-dev-96d5822c1d812ed30da035795a4408f43fe533f3.zip | |
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 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions