netdev - Re: Assigning MAC addrs to PCI based NIC's

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: <20200717170843.GB1339445@lunn.ch>
Date:   Fri, 17 Jul 2020 19:08:43 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     Tim Harvey <tharvey@...eworks.com>
Cc:     netdev <netdev@...r.kernel.org>
Subject: Re: Assigning MAC addrs to PCI based NIC's

On Fri, Jul 17, 2020 at 08:58:26AM -0700, Tim Harvey wrote:
> Greetings,
> 
> We make embedded boards that often have on-board PCIe based NIC's that
> have MAC addresses stored in an EEPROM (not within NIC's NVRAM). I've
> struggled with a way to have boot firmware assign the mac's via
> device-tree and I find that only some drivers support getting the MAC
> from device-tree anyway.
> 
> What is the appropriate way to assign vendor MAC's to a NIC from boot
> firmware, or even in userspace?

Hi Tim

>From user space you can always use

ip link set address XX:XX:XX:XX:XX:XX dev enp42s0

But that assumes the MAC driver actually supports setting its MAC
address. As with getting the MAC address from DT, this is also
optional in the driver. But i guess it is more often implemented.

I don't know of any universal method. So i think you probably do need
to work on each of the MAC drivers you are interested in, and add DT
support.

	Andrew