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
A malformed known IPv6 extension header should parse as Raw, not IPv6_Ext #2477
A malformed known IPv6 extension header should parse as Raw, not IPv6_Ext
When a dedicated parser (HOPOPT, Routing, Opts, MH, HIP) raises, IPv6._import_next_layer re-parses that header as IPv6_Ext so the walk continues. Per RFC 8200 §4 a node discards such a packet, and RFC 6564 does not prescribe skipping. Maintainer's ruling: follow the RFC.
Drop the fallback-on-failure and __generic_ext_codes__. The failed header becomes Raw (via beholder) and the walk stops there.
Keep IPv6_Ext for Shim6, which is registered to it directly and has no parser of its own.
Update the docs that describe the fallback (ipv6.py, ipv6_ext.py, the ipv6-ext-entry-paths section) and the tests that pin it.
Waits for #2464's redo to land, since both edit ipv6_ext.py.
Activity
JarryShaw commentedon Oct 30, 2026
Unblocks when #2464 reaches
review: good-to-go; both editipv6_ext.py.JarryShaw commentedon Oct 30, 2026
Unblocked (#2464 is good-to-go). Dispatched, stacked on #2464's branch since both edit
ipv6_ext.py.fix(protocols)!: parse a malformed IPv6 extension header as Raw (#2477)
fix(protocols)!: parse a malformed IPv6 extension header as Raw (#2477)…