summaryrefslogtreecommitdiff
path: root/net/netrom
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2022-01-04 12:17:35 +0000
committerDavid S. Miller <davem@davemloft.net>2022-01-04 12:17:35 +0000
commitd2d9a6d0b4c2b4d2cd07378e190469f030c7d126 (patch)
treeaf54a38b1570fc9bbade6c094f7b12d4151c86cb /net/netrom
parente8fe9e8308b227002d68d6a32bbd141386727328 (diff)
parent222a011efc839ca1f51bf89fe7a2b3705fa55ccd (diff)
Merge branch 'srv6-traceroute'
Andrew Lunn says: ==================== Fix traceroute in the presence of SRv6 When using SRv6 the destination IP address in the IPv6 header is not always the true destination, it can be a router along the path that SRv6 is using. When ICMP reports an error, e.g, time exceeded, which is what traceroute uses, it included the packet which invoked the error into the ICMP message body. Upon receiving such an ICMP packet, the invoking packet is examined and an attempt is made to find the socket which sent the packet, so the error can be reported. Lookup is performed using the source and destination address. If the intermediary router IP address from the IP header is used, the lookup fails. It is necessary to dig into the header and find the true destination address in the Segment Router header, SRH. v2: Play games with the skb->network_header rather than clone the skb v3: Move helpers into seg6.c v4: Move short helper into header file. Rework getting SRH destination address v5: Fix comment to describe function, not caller Patch 1 exports a helper which can find the SRH in a packet Patch 2 does the actual examination of the invoking packet Patch 3 makes use of the results when trying to find the socket. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/netrom')
0 files changed, 0 insertions, 0 deletions