From: Hangbin Liu <liuhangbin@gmail.com>
To: David Lebrun <dlebrun@google.com>
Cc: Andrea Mayer <andrea.mayer@uniroma2.it>, netdev@vger.kernel.org
Subject: Why we need add :: at the last when encap seg6 with inline mode?
Date: Tue, 27 Jun 2023 15:28:03 +0800 [thread overview]
Message-ID: <ZJqPg7Ck8ulDp2f+@Laptop-X1> (raw)
Hi David,
When I tried encap seg6 inline mode via iproute, I saw it added a :: address
at the last.
# ip -6 route add 1234::1234 encap seg6 mode inline segs 1::1 dev dum1
# ip -6 route show dev dum1
1234::1234 encap seg6 mode inline segs 2 [ 1::1 :: ] metric 1024 pref medium
In the iproute2 code
```
static struct ipv6_sr_hdr *parse_srh(char *segbuf, int hmac, bool encap)
{
...
if (!encap)
nsegs++;
...
```
So is there any reason we add this?
Thanks
Hangbin
next reply other threads:[~2023-06-27 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 7:28 Hangbin Liu [this message]
[not found] ` <AM6PR07MB56691CDB704895F0E13689AA9125A@AM6PR07MB5669.eurprd07.prod.outlook.com>
2023-07-04 2:48 ` R: Why we need add :: at the last when encap seg6 with inline mode? Hangbin Liu
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=ZJqPg7Ck8ulDp2f+@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andrea.mayer@uniroma2.it \
--cc=dlebrun@google.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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