Repository navigation
fix(pcapng): undefined epb_flags direction or reception values raise, so such a capture cannot round-trip #1382
Description
With #1378's LSB-0 FlagsField, a direction of 0b11 or a reception type of 5–7 raises ProtocolError. A capture carrying one can therefore be neither parsed nor rebuilt, which breaks the every-round-trip ruling. main also failed here, with ValueError/EnumValueError. Keep the wire value as an unassigned member, or in a raw field. Bits 9–11 (checksum not ready, checksum valid, TSO), which pcapng-06 Table 5 defines, should also get names instead of sitting in reserved.
Confirmed by the #1373/#1378 cross-reviews; present on main too, so not a regression of those PRs. Blocked until #1373 and #1378 merge (same PCAP-NG/PCAP modules).
Activity
JarryShaw commentedon Oct 8, 2026
Still blocked, now on a different PR. #1378 has merged, but the PCAP-NG half of #1398 (#1325, strict option lengths) is about to edit the same PCAP-NG files. Blocked until #1398 merges.
JarryShaw commentedon Oct 8, 2026
Unblocked: #1398 (and #1400) have merged. One worker is taking all the PCAP-NG follow-ups together, #1382–#1384, #1401, #1405 and #1406, because they edit the same
pcapng.pyfiles.fix(pcapng)!: PCAP-NG round-trip follow-ups (#1382, #1383, #1384, #1401…