From: "Robin Jarry" <rjarry@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, "Christophe Fontaine" <cfontain@redhat.com>,
<stable@dpdk.org>
Subject: Re: [PATCH dpdk] net: ipv6 link local compliance with rfc 4291
Date: Fri, 14 Nov 2025 17:46:42 +0100 [thread overview]
Message-ID: <DE8KJK97R8KQ.3SC0EJPIEHSP3@redhat.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F65560@smartserver.smartshare.dk>
Morten Brørup, Nov 14, 2025 at 17:14:
>> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
>> Reading the kernel source there is also special handling to include
>> device
>> id into link local address. This is to handle corner case where
>> multiple network
>> cards have same hardware MAC address.
>
> Multiple physical NICs should never have the same MAC address.
> Lots of stuff will break if they do.
> E.g. a network switch will forward packets to the NIC that most recently sent packets, so its MAC address was learned in the MAC address table in the switch.
>
> What is the use case justifying this tweak in the kernel?
Some drivers expose multiple ports sharing the same mac address.
This very is specific to certain hardware vendors. The comment here
refers to a change from 2005. I couldn't find the root commit/email.
https://github.com/jeffmahoney/linux-pre-git/commit/44993d3bb812f
> 2005/01/17 13:13:52-08:00 hch
> [IPV6]: Fix EUI64 generation on S/390.
>
> - put a dev_id field in struct net_device, so that it uses space that
> would be wasted by padding otherwise.
> - if this fields is non-null let ipv6_generate_eui64 use the algorithm
> from the QETH code to generate an EUI that's different for each
> OS instance. See code comments for details.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
I don't think DPDK should care about this.
--
Robin
> Do not use while operating a motor vehicle or heavy machinery.
next prev parent reply other threads:[~2025-11-14 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:57 Robin Jarry
2025-11-14 16:05 ` Stephen Hemminger
2025-11-14 16:08 ` Robin Jarry
2025-11-14 16:14 ` Morten Brørup
2025-11-14 16:46 ` Robin Jarry [this message]
2025-11-14 17:03 ` Stephen Hemminger
2025-11-14 16:48 ` Stephen Hemminger
2025-11-14 16:08 ` Stephen Hemminger
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=DE8KJK97R8KQ.3SC0EJPIEHSP3@redhat.com \
--to=rjarry@redhat.com \
--cc=cfontain@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).