Hello,
On Mon, Mar 23, 2020 at 8:13 PM Romain Francoise wrote:
>
> I just uploaded the backport, it may take a few days before it appears
> in the archive.
It took some time but the package finally landed in buster-backports, and now
tcpdump -r with my capture file \o/.
Many thanks,
Marc.
I just uploaded the backport, it may take a few days before it appears
in the archive.
On Sat, Mar 21, 2020 at 10:25 PM Romain Francoise wrote:
> Thanks for the report. Wireshark has its own implementation of the
> PcapNg format, so it's not unexpected that it behaves differently than
> tcpdump.
>
> The fix is a bit too intrusive for a stable update, especially for a
> minor bug
Hi,
Thanks for the report. Wireshark has its own implementation of the
PcapNg format, so it's not unexpected that it behaves differently than
tcpdump.
The fix is a bit too intrusive for a stable update, especially for a
minor bug like this. I will simply do a buster backport of libpcap
1.9.1-2
Package: tcpdump
Version: 4.9.3-1~deb10u1
Severity: normal
Dear Maintainer,
I tried to display a pcapng capture with `tcpdump -r` but failed
with:
> tcpdump: invalid interface capture length 524288, bigger than maximum of
> 262144
The file is correctly read by wireshark on the same machine.
5 matches
Mail list logo
