From: Oliver Neukum <oneukum@suse.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: question on random MAC in usbnet
Date: Thu, 16 Nov 2023 11:14:49 +0100 [thread overview]
Message-ID: <53b66aee-c4ad-4aec-b59f-94649323bcd6@suse.com> (raw)
Hi,
I am wondering about the MAC address usbnet is handing
out. In particular why that is a singular address.
Frankly that seems plainly wrong. A MAC is supposed
to be unique, which is just fundamentally incompatible
to using the same MAC for multiple devices, as usbnet
currently potentially does.
Do you think that behavior should be changed to using
a separate random MAC for each device that requires it?
Regards
Oliver
next reply other threads:[~2023-11-16 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 10:14 Oliver Neukum [this message]
2023-11-16 11:31 ` question on random MAC in usbnet Bjørn Mork
2023-11-16 12:32 ` Oliver Neukum
2023-11-19 11:09 ` David Laight
2023-11-19 16:13 ` Andrew Lunn
2023-11-20 11:06 ` Oliver Neukum
2023-11-20 16:48 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53b66aee-c4ad-4aec-b59f-94649323bcd6@suse.com \
--to=oneukum@suse.com \
--cc=bjorn@mork.no \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).