[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8201b72-90c4-d8e6-65b9-b7f7ed55f0f5@gmail.com>
Date: Sun, 27 Oct 2019 11:16:25 -0600
From: David Ahern <dsahern@...il.com>
To: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, jakub.kicinski@...ronome.com,
stephen@...workplumber.org, roopa@...ulusnetworks.com,
dcbw@...hat.com, nikolay@...ulusnetworks.com, mkubecek@...e.cz,
andrew@...n.ch, parav@...lanox.com, saeedm@...lanox.com,
f.fainelli@...il.com, sd@...asysnail.net, sbrivio@...hat.com,
pabeni@...hat.com, mlxsw@...lanox.com
Subject: Re: [patch iproute2-next v5 0/3] ip: add support for alternative
names
On 10/24/19 4:20 AM, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...lanox.com>
>
> This patchset adds support for alternative names caching,
> manipulation and usage.
>
something is still not right with this change:
$ ip li add veth1 type veth peer name veth2
$ ip li prop add dev veth1 altname veth1_by_another_name
$ ip li sh dev veth1
15: veth1@...h2: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state
DOWN mode DEFAULT group default qlen 1000
link/ether 1e:6e:bc:26:52:f6 brd ff:ff:ff:ff:ff:ff
altname veth1_by_another_name
$ ip li sh dev veth1_by_another_name
Device "veth1_by_another_name" does not exist.
$ ip li set dev veth1_by_another_name up
Error: argument "veth1_by_another_name" is wrong: "dev" not a valid ifname
Powered by blists - more mailing lists