From: patchwork-bot+netdevbpf@kernel•org
To: Andrew Lunn <andrew@lunn•ch>
Cc: davem@davemloft•net, kuba@kernel•org, yoshfuji@linux-ipv6•org,
dsahern@kernel•org, willemb@google•com, prestwoj@gmail•com,
justin.iurman@uliege•be, praveen5582@gmail•com, Jason@zx2c4•com,
edumazet@google•com, netdev@vger•kernel.org
Subject: Re: [PATCH v5 net-next 0/3] Fix traceroute in the presence of SRv6
Date: Tue, 04 Jan 2022 12:40:10 +0000 [thread overview]
Message-ID: <164130001053.24992.6088004457600780480.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220103171132.93456-1-andrew@lunn.ch>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Mon, 3 Jan 2022 18:11:29 +0100 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v5,net-next,1/3] seg6: export get_srh() for ICMP handling
https://git.kernel.org/netdev/net/c/fa55a7d745de
- [v5,net-next,2/3] icmp: ICMPV6: Examine invoking packet for Segment Route Headers.
https://git.kernel.org/netdev/net/c/e41294408c56
- [v5,net-next,3/3] udp6: Use Segment Routing Header for dest address if present
https://git.kernel.org/netdev/net/c/222a011efc83
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-04 12:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 17:11 [PATCH v5 net-next 0/3] Fix traceroute in the presence of SRv6 Andrew Lunn
2022-01-03 17:11 ` [PATCH v5 net-next 1/3] seg6: export get_srh() for ICMP handling Andrew Lunn
2022-01-03 17:31 ` David Ahern
2022-01-03 20:52 ` Willem de Bruijn
2022-01-03 17:11 ` [PATCH v5 net-next 2/3] icmp: ICMPV6: Examine invoking packet for Segment Route Headers Andrew Lunn
2022-01-03 17:34 ` David Ahern
2022-01-03 20:55 ` Willem de Bruijn
2022-01-03 17:11 ` [PATCH v5 net-next 3/3] udp6: Use Segment Routing Header for dest address if present Andrew Lunn
2022-01-03 17:35 ` David Ahern
2022-01-03 20:55 ` Willem de Bruijn
2022-01-04 12:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164130001053.24992.6088004457600780480.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=Jason@zx2c4$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=justin.iurman@uliege$(echo .)be \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=praveen5582@gmail$(echo .)com \
--cc=prestwoj@gmail$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox