On Tue, Oct 26, 2021 at 12:03:49AM -0500, Bob Pearson wrote: > I spent some time looking at the current code for attach multicast and it seems likely not to work. Unfortunately there isn't very much test code for multicast over RoCEv2. Currently the rxe receive code maps all ipv4 multicast addresses ([224-239].x.x.x) to IPV6 unicast addresses using the 46 mapping 0::0000:ffff:aabb:ccdd where the IPV4 address is aa.bb.cc.dd. > This is then mapped to a 48 bit MAC address using the IPV6 to MAC mapping > > IPV6 mcast addr = FFts:xxxx:xxxx:xxxx::xxxx:xxxx:aabb:ccdd -> 33, 33, aa, bb, cc, dd. > The 33, 33 identifies the mac address as a mapped IPV6 address. The real mapping from > IPV4 address to MAC address is > > Ea.bb.cc.dd -> 01, 00, 5E, bb, cc, dd with the msb of the bb set to zero. The 01, 00, 5E > identifies the address as a mapped IPV4 address. The mapped MAC addresses create a filter > to allow the (non unique sets of) multicast addresses to be accepted by the NIC. > > Real IPV4 multicast traffic is not likely to be accepted by this. > > Is there any documentation on how mcast is supposed to work for RoCEv2? Or an expert > I can direct questions to? Can't say I know which is right either I'd rather expect someone creating a rocev2 IPv4 multicast group to stay in ipv4 land though The transform to IPV6 multicast is something that rocev1 only should do. Jason
