[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241230164958.5f99eb90@pi5>
Date: Mon, 30 Dec 2024 16:49:58 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Ido Schimmel <idosch@...dia.com>
Cc: <netdev@...r.kernel.org>, <dsahern@...il.com>, <petrm@...dia.com>,
<gnault@...hat.com>
Subject: Re: [PATCH iproute2-next v2 2/3] ip: route: Add IPv6 flow label
support
On Mon, 30 Dec 2024 10:58:09 +0200
Ido Schimmel <idosch@...dia.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?
Powered by blists - more mailing lists