Your message dated Tue, 2 Aug 2016 11:03:13 +0200 with message-id <cak0odpwpz5nhbttjc6xef7wtfo7d88s-um7ycd-zddu1mo6...@mail.gmail.com> and subject line Re: Bug#681478: wireshark-common: mergecap generates unusable file if interface index 0 has no packets has caused the Debian Bug report #681478, regarding wireshark-common: mergecap generates unusable pcapng file if interface index 0 has no packets to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 681478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681478 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wireshark-common Version: 1.8.0-1 Tags: upstream mergecap: Error reading <file>: The file appears to be damaged or corrupt. (pcapng: interface index 1024 is not less than interface count 1.) Upstream report: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7381 Perhaps the previous version package should be made available again, until this is fixed in upstream. Regards, Phil
--- End Message ---
--- Begin Message ---Control: fixed -1 2.0.0~rc3+g841d5e1-1 Somehow I forgot closing this bug when it got fixed. 2012-07-17 14:42 GMT+02:00 Philipp Marek <[email protected]>: >> > The problem occurs only when mergecap creates pcapng files. >> > The following works fine for me: >> > $ mergecap -F libpcap >> >> I'll try that, thank you for the hint. > I can confirm that if I put "-F libpcap" on all tools (editcap, mergecap, > tshark) I can open the resulting files.
--- End Message ---
