[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180418.212002.370060356228679393.davem@davemloft.net>
Date: Wed, 18 Apr 2018 21:20:02 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: stephen@...workplumber.org
Cc: haiyangz@...rosoft.com, netdev@...r.kernel.org,
sthemmin@...rosoft.com
Subject: Re: [PATCH net-next] hv_netvsc: propogate Hyper-V friendly name
into interface alias
From: Stephen Hemminger <stephen@...workplumber.org>
Date: Tue, 17 Apr 2018 14:25:30 -0700
> This patch implement the 'Device Naming' feature of the Hyper-V
> network device API. In Hyper-V on the host through the GUI or PowerShell
> it is possible to enable the device naming feature which causes
> the host to make available to the guest the name of the device.
> This shows up in the RNDIS protocol as the friendly name.
>
> The name has no particular meaning and is limited to 256 characters.
> The value can only be set via PowerShell on the host, but could
> be scripted for mass deployments. The default value is the
> string 'Network Adapter' and since that is the same for all devices
> and useless, the driver ignores it.
>
> In Windows, the value goes into a registry key for use in SNMP
> ifAlias. For Linux, this patch puts the value in the network
> device alias property; where it is visible in ip tools and SNMP.
>
> The host provided ifAlias is just a suggestion, and can be
> overridden by later ip commands.
>
> Also requires exporting dev_set_alias in netdev core.
>
> Signed-off-by: Stephen Hemminger <sthemmin@...rosoft.com>
This looks fine, applied, thanks.
Powered by blists - more mailing lists