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
Commit 6aeba80
Browse filesBrowse the repository at this point in the historyBrowse files
Third-party engines are best effort (#1687), so the pypcapfile code that
exists only to match the default engine comes out:
- revert #1682, #1600, #1575 and #1535, and the pypcapfile hunks of #1655,
#1608 and #1605: reading loopback and raw-IP link types, the frame layer
bound, the VLAN and tunnel walks, keying tunnelled TCP by the innermost
header, stepping over AH and extension headers, and checking options
with the default engine's parsers
- keep the helpers the dpkt and scapy adapters import, unchanged, until
their own reverts drop them; their docstrings no longer say pypcapfile
asks the default engine's parsers too
- re-land #1576, #1577, #1590 and #1591 as guards in _network and
_transport, #1513's once-per-capture warning for TCP straight over
IPv6, and #1667's packet2dict fix: an undecoded frame is reported as
its octets, not as hex text twice as long
- keep #1569's record reader and #1690's packet2timestamp
- delete the three test modules those reverts added, the pypcapfile
timestamp agreement class, and #1682's link-type warning test; the
re-landed guards' tests assert constants
- drop what the reverts removed from the docs, READ_LINKTYPES included,
and say that TCP behind a VLAN tag, in a tunnel or behind an
extension header (an IPv6 one, or AH in IPv4) is now left out
without a warning
The pypcapfile modules, test_new_engine_parity_runtime.py,
test_engine_runtime.py, the timestamp module and the project guards pass
on 3.11 (pypcapfile 0.12.0) and 3.14.
0 commit comments