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(ipv6): a jumbogram's payload is not dissected and is reported as trailer #1434
Describe the bug
An IPv6 jumbogram (Payload Length 0 plus a Hop-by-Hop Jumbo Payload option, RFC 2675) does not parse its payload. On main the next layer is NoPayload and the rebuild is lossy: 72 → 40 bare, 86 → 54 inside Ethernet. #1431 makes the bytes round-trip exactly, but only by reporting the whole jumbo payload as trailer.
Expected behavior
When a Jumbo option is present with Payload Length 0, the Jumbo Payload Length gives the payload extent. The payload is dissected as the next header, and only octets beyond it are trailer.
Found by the #1431 cross-review. Blocked until#1431 merges, since it owns protocols/{,schema/,data/}internet/ipv6.py.
Activity
JarryShaw commentedon Oct 8, 2026
Unblocked: #1431 merged (
0ace21349), soprotocols/{,schema/,data/}internet/ipv6.pyis free. Moving topending.JarryShaw commentedon Oct 8, 2026
A worker is on it now, on branch
fix/1434-ipv6-jumbogram-payload.fix(ipv6): dissect a jumbogram's payload up to its Jumbo Payload Leng…