Multicast MAC in Source MAC Address Field
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
|||||||||||||||||||||||||
|
Posted by Matthias Schaerer on August 30, 2005, 5:13 pm
Please log in for more thread options Hi, is it allowed/forbidden to send an Ethernet Source MAC address field with a multicast MAC address in it? Any references? (RFCs, IEEE doks, other??) I've been searching for a while now and the only thing I found out is that Cisco doesn't like it and calls it illegal but I did not find the law yet... Thanks Mat | |||||||||||||||||||||||||
|
Posted by Albert Manfredi on August 31, 2005, 9:38 am
Please log in for more thread options Matthias Schaerer wrote: This is discussed in Radia Perlman's Interconnections (ISBN 0-201-56332-0), Chapter 4, and in IEEE 802.1D Annex C. In short, an address that looks like a MAC multicast source address *can* be used, but it's meant for a very special purpose. It is used by a host to denote that "source routing" instructions are included in the MAC frame. (Note: this is Layer 2 source "routing" we're talking about, not the IP option). The "multicast bit" is set in the MAC source address, to indicate source routing. But instead of being called G/I bit, as it is when it's associated with the MAC destination address, in this case it is called RII, for Routing Information Indicator. Thing is, though, this applies to IEEE 802.5 and FDDI (respectively sections C.2.5.1 and C.2.5.2). No mention of Ethernet support. (If you want to use source routing with Ethernet, don't despair. You don't code the RII bit in the MAC source address. Instead, you use the IEEE 802.1Q "tagged frame" format, and set the CFI bit. When the CFI bit is set in Ethernet tagged frames, that means that there is E-RIF included in the extended Ethernet header, i.e. routing information field.) So that was a bit of a side trip. I think, in short, the RII bit is not set in Ethernet MAC source addresses. But it can be set in Token Ring or FDDI, and it makes the MAC source address look like a multicast address. Bert | |||||||||||||||||||||||||
|
Posted by glen herrmannsfeldt on August 31, 2005, 12:15 pm
Please log in for more thread options
Albert Manfredi wrote: (snip regarding multicast bit in source addresses) > So that was a bit of a side trip. I think, in short, the RII bit is not
> set in Ethernet MAC source addresses. But it can be set in Token Ring > or FDDI, and it makes the MAC source address look like a multicast > address. And what about packets bridged between FDDI or TR and ethernet with such bit set? -- glen | |||||||||||||||||||||||||
|
Posted by Albert Manfredi on August 31, 2005, 1:04 pm
Please log in for more thread options
glen herrmannsfeldt wrote: > Albert Manfredi wrote:
> (snip regarding multicast bit in source addresses) > > > So that was a bit of a side trip. I think, in short, the RII bit is not
> > set in Ethernet MAC source addresses. But it can be set in Token Ring > > or FDDI, and it makes the MAC source address look like a multicast > > address. >
> And what about packets bridged between FDDI or TR and ethernet with > such bit set? The answer must be, the source MAC address lowest bit is returned to 0, the frame is coded up like a 802.1Q tagged Ethernet frame, and the CFI bit is set in the extended header, to show that source "routing" info is also added to the Ethernet header. And the routing info from the source-routed TR or FDDI frame is copied into the E-RIF of the extended Ethernet header. But that might just be a textbook answer. I don't know whether switch manufacturers bother with this in practice. Bert | |||||||||||||||||||||||||
|
Posted by Albert Manfredi on August 31, 2005, 1:10 pm
Please log in for more thread options
> > And what about packets bridged between FDDI or TR and ethernet with
> > such bit set? >
> The answer must be, the source MAC address lowest bit is returned to 0, Shucks. That's "the lowest bit of the first byte of the source MAC address ..." > the frame is coded up like a 802.1Q tagged Ethernet frame, and the CFI
> bit is set in the extended header, to show that source "routing" info > is also added to the Ethernet header. And the routing info from the > source-routed TR or FDDI frame is copied into the E-RIF of the extended > Ethernet header. > > But that might just be a textbook answer. I don't know whether switch > manufacturers bother with this in practice. > > Bert | |||||||||||||||||||||||||
| Similar Threads | Posted |
| Multicast MAC in Source MAC Address Field | August 30, 2005, 5:13 pm |
| Source MAC address per IP packet | June 15, 2008, 3:02 pm |
| Picking an IP multicast address | October 29, 2004, 1:03 pm |
| Multicast MAC and Unicast IP Address | August 18, 2005, 7:54 pm |
| Multicast test bed | October 18, 2004, 8:51 am |
| multicast, MAC ending with 00:96 ? | August 14, 2005, 12:55 am |
| ARP reply containing a multicast MAC OK? | March 19, 2007, 4:50 pm |
| Multicast pruning | July 2, 2008, 7:24 am |
| Multicast VLAN Id | July 14, 2008, 7:41 am |
| provide me Source code of IGMPv2 | May 26, 2006, 2:37 am |
| Maximum MAC multicast filters? | October 5, 2005, 8:48 am |
| Does someone have IGMP snooping source code for Bridge?? | May 30, 2006, 9:06 am |
| Extreme Networks 300-48 Multicast issues | January 11, 2005, 1:55 am |
| Looking for open-source home DSL gateway software & hardware to run it | November 1, 2007, 10:38 am |
| cable management - source for velcro straps with screw hole? | July 20, 2004, 8:04 pm |
>
> is it allowed/forbidden to send an Ethernet Source MAC address field
> with a multicast MAC address in it?
>
> Any references? (RFCs, IEEE doks, other??)
>
> I've been searching for a while now and the only thing I found out is
> that Cisco doesn't like it and calls it illegal but I did not find the
> law yet...