From: Oliver Neukum <oneukum@suse.com>
To: "David Laight" <David.Laight@ACULAB.COM>,
"'Bjørn Mork'" <bjorn@mork.no>,
"Oliver Neukum" <oneukum@suse.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: question on random MAC in usbnet
Date: Mon, 20 Nov 2023 12:06:55 +0100 [thread overview]
Message-ID: <a384af65-7fc0-4af8-9c86-b838994437c4@suse.com> (raw)
In-Reply-To: <64dfec9e75a744cf8e7f50807140ba9a@AcuMS.aculab.com>
On 19.11.23 12:09, David Laight wrote:
> It might cause grief when a USB device 'bounces' [1].
> At the moment it will pick up the same 'random' MAC address.
> But afterwards it will change.
>
> So you might want to save the MAC on device removal and
> re-use it on the next insert.
That means that the MAC a device would get depends on the
sequence of plugs and unplugs. That seems ... interesting.
Regards
Oliver
next prev parent reply other threads:[~2023-11-20 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 10:14 question on random MAC in usbnet Oliver Neukum
2023-11-16 11:31 ` 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 [this message]
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=a384af65-7fc0-4af8-9c86-b838994437c4@suse.com \
--to=oneukum@suse.com \
--cc=David.Laight@ACULAB.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