[dpd, mcast] Tighten multicast group and source validation - #364
Open
zeeshanlakhani wants to merge 1 commit into
Open
[dpd, mcast] Tighten multicast group and source validation#364zeeshanlakhani wants to merge 1 commit into
zeeshanlakhani wants to merge 1 commit into
Conversation
zeeshanlakhani
force-pushed
the
zl/mcast-validation
branch
from
September 3, 2026 04:09
245390d to
a8b5214
Compare
This PR constrains group and SSM source validation based on a variety of specs, linked throughout the PR. Previously, DPD was accepting groups and (S, G) sources that no packet could actually exercise, including ones that can never leave a host/link, group IDs outside of what hosts may try to allocate, or, worst, sources a switch can't forward. Here's the list (the first classifier one was the most obvious): | address | verdict | spec | |--------------------------------|---------|-------------------------------| | ff3x::/32 in ff30::/12 only | is SSM | RFC 4607 §1; RFC 3306 is ASM | | 232.0.0.0/24 | reject | RFC 4607 §4.3 (reserved) | | ff3x:: group ID < 0x80000000 | reject | RFC 4607 §1, RFC 3307 §4.3.2 | | v6 scopes other than 4/5/8/e | reject | RFC 7346; no Ethernet realm | | class E (240.0.0.0/4) source | reject | RFC 6890 "Source: False" | | 0.0.0.0/8 source | reject | RFC 6890 "Forwardable: False" | | v4-mapped/compat/NAT64 source | reject | aliases IPv4 / no mcast in it | | 100.64.0.0/10 source | allow | RFC 6598, operator-internal | | source/group family mismatch | reject | (local choice) |
zeeshanlakhani
force-pushed
the
zl/mcast-validation
branch
from
September 3, 2026 12:52
a8b5214 to
a7a2f5c
Compare
zeeshanlakhani
changed the title
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
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.
This PR constrains group and SSM source validation based on a variety of specs,
linked throughout the PR. Previously, DPD was accepting groups and (S, G) sources that no packet could actually exercise, including ones that can never leave a host/link, group IDs outside of what hosts may try to allocate, or, worst, sources a switch can't forward.
Here's the list (the first classifier one was the most obvious):