You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(internet): a cut IGMPv3 message parsed directly does not rebuild as captured #2660
IGMPv3(raw, len(raw)) on octets cut short does not rebuild as captured, for both Reports and Queries. The short read is recorded only on the nested schema, so keep_short_read never carries it to the layer. Parsing through IPv4 is not affected, because there the declared length reaches the schema. The #2650 worker found this, and it has not been reproduced independently.
To do: reproduce on main with #2650 merged, carry the nested schema's short-read marker up so a direct parse rebuilds exactly, and test both message types.
Blocked on #2650's PR, which owns igmpv3.py and its schema. Unblocks when that PR merges.
#2662 has merged, so the IGMPv3 short-read handling is on main. Unblocked. A worker is lifting the nested schema's short-read marker, so a direct parse of a cut message rebuilds as captured.
Activity
JarryShaw commentedon Nov 2, 2026
#2662 has merged, so the IGMPv3 short-read handling is on
main. Unblocked. A worker is lifting the nested schema's short-read marker, so a direct parse of a cut message rebuilds as captured.JarryShaw commentedon Nov 2, 2026
The PR is #2672.
fix(internet): rebuild an IGMPv3 message cut short and parsed on its …