Re: I-D Action: draft-ietf-mboned-ieee802-mcast-problems-05.txt

As I understand it, if it has been unicast-mapped, the Ethernet MAC address
will be your NIC's MAC address, instead of starting with 01-00-5E and
finishing with the last 23 bits of the group address.  (Or 33-33- and
finishing with the last 32 bits of the group, for IPv6.)

I think these are where the normative behavior for normal multicast is
described, and the m2u behavior just uses the unicast ethernet MAC instead:
https://tools.ietf.org/html/rfc1112#section-6.4
https://tools.ietf.org/html/rfc2464#section-7

Thanks for taking a look!

-Jake

On 2019-05-10, 23:11, "Mikael Abrahamsson" <[email protected]> wrote:

    On Sat, 11 May 2019, Holland, Jake wrote:
    
    > Some of them are based on OpenWRT or LEDE (not always obviously), and
    > from the patchworks message on the initial upstream submission, it looks
    > like those have had default enabled support for mc2uc on AP interfaces
    > since the builds from at least about early 2016 or so:
    > https://patchwork.kernel.org/patch/9494055/
    
    I have an OpenWrt 18.06.2 device at home I can test with. How can I check 
    on a MacOS or Linux machine whether the packet I received was sent as 
    unicast or multicast wifi packet?
    
    -- 
    Mikael Abrahamsson    email: [email protected]
    

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned