[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d88376a7-3e12-fcca-a61e-58747622328d@gmail.com>
Date: Thu, 22 Sep 2022 14:28:03 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <vladimir.oltean@....com>,
Stephen Hemminger <stephen@...workplumber.org>
Cc: Jakub Kicinski <kuba@...nel.org>, Andrew Lunn <andrew@...n.ch>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
David Ahern <dsahern@...nel.org>,
Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and
change DSA master
On 9/22/22 13:36, Vladimir Oltean wrote:
> On Thu, Sep 22, 2022 at 01:28:16PM -0700, Stephen Hemminger wrote:
>> Not sure where choice of "via" came from. Other network os's use "next-hop"
>> or just skip having a keyword.
>
> Jakub was saying:
>
> $ ip link set dev swp0 type dsa via eth0
>
> meaning: "make the locally terminated traffic of swp0 go via (through) eth0".
> No direct relationship with IP nexthops.
>
> It avoids saying that eth0 is a DSA master.
That part was clear (at least to me). I read Stephen's questions as how
did we come up with the keyword "via" to designated gateways in the
first place when other network operating systems use "next-hop".
I, too, think of "via" as a printed circuit board term, so using
"conduit" seems more in line with the vocabulary I could retain my
muscle memory with.
--
Florian
Powered by blists - more mailing lists