Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARP: resolve IP multicast #18

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

sergachev
Copy link

According to RFC1112, addresses 224.0.0.0 – 239.255.255.255 (starting 0b1110) should be resolved by placing the low-order 23-bits of the IP address into the low-23 bits of the Ethernet multicast address 01-00-5E-00-00-00. Another explanation here.
This allows, for instance, sending multicast PTP packets to 224.0.1.129, which maps to 01:00:5e:00:01:81.

@gncemre23
Copy link

According to RFC1112, addresses 224.0.0.0 – 239.255.255.255 (starting 0b1110) should be resolved by placing the low-order 23-bits of the IP address into the low-23 bits of the Ethernet multicast address 01-00-5E-00-00-00. Another explanation here. This allows, for instance, sending multicast PTP packets to 224.0.1.129, which maps to 01:00:5e:00:01:81.

Do we need to implement IGMP protocol to receive the multicast IP packets?

@sergachev
Copy link
Author

Do we need to implement IGMP protocol to receive the multicast IP packets?

If your switch / router does IGMP snooping - yes, your device needs to send an IGMP join message to start receiving multicast.

@gncemre23
Copy link

Do we need to implement IGMP protocol to receive the multicast IP packets?

If your switch / router does IGMP snooping - yes, your device needs to send an IGMP join message to start receiving multicast.

Thank you, that saves my life :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants