lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z3OZgsoGjFLiCxXH@shredder>
Date: Tue, 31 Dec 2024 09:13:06 +0200
From: Ido Schimmel <idosch@...dia.com>
To: Stephen Hemminger <stephen@...workplumber.org>
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, Dec 30, 2024 at 04:49:58PM -0800, Stephen Hemminger wrote:
> 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?

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ