Repository navigation
fix(toolkit): dpkt gives no IPv4 reassembly input for IPv4 carried in IPv6 #1615
Description
With engine='dpkt', IPv4 carried inside IPv6 (next header 4, RFC 2473) gets no IPv4 reassembly input.
Repro on main (d6f627481): two fragments of one 24-octet IPv4 datagram inside IPv6.
| Engine | IPv4 inputs | Datagrams reassembled |
|---|---|---|
| default | 2 | 1 (complete) |
| dpkt | 0 | 0 |
| scapy | 2 | 1 (complete) |
Plain IPv4 fragments (control) give 2 inputs and 1 datagram on every engine.
Cause: pcapkit/toolkit/dpkt.py:588 sets ipv4 = None if hasattr(network, 'extension_hdrs') else network. The IPv6 network layer is never looked inside.
Expected: dpkt hands over the first IPv4 layer of the frame, as the default engine does.
Found by the #1614 cross-review; I reproduced it. Blocked until #1614 merges, because it edits pcapkit/toolkit/dpkt.py.
Activity
JarryShaw commentedon Oct 10, 2026
Blocked until #1614 merges, because it edits
pcapkit/toolkit/dpkt.py.JarryShaw commentedon Oct 10, 2026
Unblocked: #1614 merged. A worker is on it together with #1616, since both are in dpkt's
ipv4_reassembly.fix(toolkit): dpkt hands IPv4 reassembly what the default engine does (…
test(toolkit): drop the DF workarounds #1622 made stale in the #1607 …