Wireshark-bugs: [Wireshark-bugs] [Bug 8046] Decodes FCoE Group Multicast MAC address as Broadcom
Guy Harris
changed
bug 8046
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
RESOLVED
|
| Resolution |
---
|
FIXED
|
Comment # 1
on bug 8046
from Guy Harris
To quote IEEE Std 802-1990, IEEE Standards for Local and Metropolitan Area
Networks: Overview and Architecture:
5.1 Organizationally Unique Identifier
5.1.1 Concept. Organizationally Unique Identifiers allow a general means
of assuring unique identifiers for a number of purposes. Currently, the IEEE
assigns Organizationally Unique Identifiers to be used for generating LAN MAC
addresses and protocol identifiers. Assuming correct administration by the
assignee, the LAN MAC addresses and protocol identifiers will be universally
unique.
The Organizationally Unique Identifier is 24 bits in length and its bit
pat- tern is shown below. Organizationally Unique Identifiers are assigned as
24 bit values with both values (0,1) being assigned to the first bit and the
second bit being set to 0. The second bit of the Organizationally Unique
Identifier being set to 0 indicates that the assignment is universal.
Organizationally Unique Identifiers with the second bit set to 1 are locally
assigned and have no rela- tionship to the IEEE-assigned values (as described
herein).
5.2 48-Bit Universal LAN MAC Addresses
5.2.1 Concept. The concept of universal addressing is basedon the idea
that all potential members of a network need to have a unique identifier (if
they are going to coexist in the network). The advantage of a universal address
is that a node with such an address can be attached to any LAN in the world
with an assurance that its address is unique.
A 48-bit Universal Address consist of two parts. The first 24 bits
correspond to the Organizationally Unique Identifier as assigned by the IEEE,
except that the assignee may set the first bit to 1 for group addresses or set
it to 0 for individual addresses.
which seems to indicate that the 0x01 bit in the first octet of a MAC address
is not part of the OUI, and thus that both 00:10:18 and 01:10:18 correspond to
Broadcom. If "01:10:18 is reserved as an FCoE group identifier", then either
1) I'm misinterpreting IEEE Std 802-1990;
2) there's a newer version of the standard that says something different;
3) Broadcom agreed to allow their OUI to be used for FCOE;
4) somebody who didn't understand IEEE Std 802-1990 picked 01:10:18 as an
FCOE group identifier.
The answer is, in fact, 3):
http://www.t11.org/ftp/t11/pub/fc/bb-5/08-334v0.pdf
The problem can be fixed for the addresses given in that PDF by adding those
addresses to wka.tmpl and regenerating the manuf file:
01-10-18-01-00-00 All-FCoE-MACs
01-10-18-01-00-01 All-ENode-MACs
01-10-18-01-00-02 All-FCF-MACs
Adding an entry for 01-10-18/24 to wka.tmpl:
01-10-18-00-00-00/24 FCoE-group
and regenerating the manuf file will cause all *unassigned* addresses in that
range to be shown as FCoE-group_xx:xx:xx or something such as that.
Fixed in rev 46386.
You are receiving this mail because:
- You are watching all bug changes.
