mrib: receive_mrt: workaround for RTL8373 queries #23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes the following warning caused by RTL8373 sending IGMP queries without including the mandatory IPv4 Router Alert option: mrib_receive_mrt: ignoring invalid IGMP-message of type 11 from <ip> on <ifindex> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Noltari
force-pushed
the
rtl8373-igmp-query-workaround-v2
branch
from
803fcb5 to
81f90c9
Compare
Member
Author
|
For reference, I've attached the IGMP Query sent by my KP-9000-9XHML-X (FW V100.9.21): |
Member
Author
|
@sbyx I know this doesn't comply with RFC3376 section 9.1, but what do you think about adding this exception? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the following warning caused by RTL8373 sending IGMP queries without including the mandatory IPv4 Router Alert option:
mrib_receive_mrt: ignoring invalid IGMP-message of type 11 from on
Alternative to #22