From: Ido Schimmel <idosch@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, dsahern@gmail.com, petrm@nvidia.com,
gnault@redhat.com
Subject: Re: [PATCH iproute2-next v2 2/3] ip: route: Add IPv6 flow label support
Date: Tue, 31 Dec 2024 09:13:06 +0200 [thread overview]
Message-ID: <Z3OZgsoGjFLiCxXH@shredder> (raw)
In-Reply-To: <20241230164958.5f99eb90@pi5>
On Mon, Dec 30, 2024 at 04:49:58PM -0800, Stephen Hemminger wrote:
> On Mon, 30 Dec 2024 10:58:09 +0200
> Ido Schimmel <idosch@nvidia.com> wrote:
>
> > @@ -2129,6 +2129,14 @@ static int iproute_get(int argc, char **argv)
> > invarg("Invalid \"ipproto\" value\n",
> > *argv);
> > addattr8(&req.n, sizeof(req), RTA_IP_PROTO, ipproto);
> > + } else if (strcmp(*argv, "flowlabel") == 0) {
> > + __be32 flowlabel;
> > +
> > + NEXT_ARG();
> > + if (get_be32(&flowlabel, *argv, 0))
> > + invarg("invalid flowlabel", *argv);
> > + addattr32(&req.n, sizeof(req), RTA_FLOWLABEL,
> > + flowlabel);
> > } else {
> > inet_prefix addr;
> >
>
> What about displaying flow label with the ip route command?
The flow label is not a route attribute and it is not present in
RTM_NEWROUTE messages. It is provided as an input to the route lookup
process in RTM_GETROUTE messages.
next prev parent reply other threads:[~2024-12-31 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 8:58 [PATCH iproute2-next v2 0/3] Add flow label support to ip-rule and route get Ido Schimmel
2024-12-30 8:58 ` [PATCH iproute2-next v2 1/3] Sync uAPI headers Ido Schimmel
2024-12-30 8:58 ` [PATCH iproute2-next v2 2/3] ip: route: Add IPv6 flow label support Ido Schimmel
2024-12-31 0:49 ` Stephen Hemminger
2024-12-31 7:13 ` Ido Schimmel [this message]
2024-12-30 8:58 ` [PATCH iproute2-next v2 3/3] iprule: Add " Ido Schimmel
2025-01-01 1:30 ` [PATCH iproute2-next v2 0/3] Add flow label support to ip-rule and route get patchwork-bot+netdevbpf
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=Z3OZgsoGjFLiCxXH@shredder \
--to=idosch@nvidia.com \
--cc=dsahern@gmail.com \
--cc=gnault@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).