Repository navigation
fix(toolkit): pypcapfile engine silently leaves TCP over IPv6 out of reassembly and tracing #1513
Description
_network() in pcapkit/toolkit/pypcapfile.py:262 returns only a decoded IPv4 layer, so tcp_reassembly (:540) and tcp_traceflow (:603) skip TCP-over-IPv6 frames without a warning.
The #1508 worker measured tcp.pcap: the default engine traces flows [(2, 6), (3,), (4, 5)], while pypcapfile traces only [(2, 6)]. http6.cap, stream.pcap and test.pcap are affected the same way.
Expected: handle IPv6, or warn that the frames are skipped, as the engine already does when it declines IPv6 reassembly.
Activity
JarryShaw commentedon Oct 9, 2026
Blocked until #1508 merges. That PR adds this defect's known-failure row in
tests/foundation/engines/test_engine_agreement_runtime.py, and a fix has to delete that row, so the fix waits for the row to exist onmain.JarryShaw commentedon Oct 9, 2026
Unblocked: #1508 has merged, so this defect's known-failure row is on
main. A worker is on the fix, and the fix PR deletes the row.fix(toolkit): the pypcapfile engine warns that it leaves TCP over IPv…
fix(toolkit): the pypcapfile engine warns that it leaves TCP over IPv…
fix(toolkit): the pypcapfile engine warns that it leaves TCP over IPv…
fix(toolkit): the pypcapfile engine warns that it leaves TCP over IPv…
refactor(toolkit): revert pypcapfile's agreement-only code (#1708) (#…