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

IGMPv3 group record states not handled properly #43

Closed
troglobit opened this issue Dec 22, 2020 · 0 comments
Closed

IGMPv3 group record states not handled properly #43

troglobit opened this issue Dec 22, 2020 · 0 comments
Assignees
Milestone

Comments

@troglobit
Copy link
Owner

Group record states other than IS_EX({})/TO_EX({}) and IS_IN({})/TO_IN({}) are not handled properly in mrouted.

The IGMPv3 support in mrouted is cannot be fully supported, because DVMRP does not have any kind of source tracking, but record states for IS_EX({x})/TO_EX({x}) and IS_IN({x})/TO_IN({x}) should be handled gracefully according to RFC5790. I.e., translated to (*,G) join/leave where appropriate and ignored otherwise.

The pimd igmp_proto.c:accept_membership_report() function has a good example of how this can be handled. Note, it handles sources which mrouted does not. So cases where sources are handled do not apply and need to be translated.

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

No branches or pull requests

1 participant