Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12526] Wireshark doesn't separate pseudoheader lengths fro

Date: Sat, 18 Jun 2016 01:51:56 +0000

Comment # 6 on bug 12526 from
(In reply to Anthony Coddington from comment #4) 
> (Heading off to meet somebody for dinner; I'll continue this in the next
> comment.  Confirming, and classifying as an "enhancement", as the behavior
> might be wrong - and I'd say it is - but it's not as if we "intended"
> something else.  Also raising the priority.)

Still thinking about it.

We want to preserve the ability of file and packet dissectors to run
pcap/pcapng file payload or rpcap/other remote capture protocol payload through
the standard dissector mechanism, so we don't want to have some stuff done
*only* by wiretap.

However, it might be nice if, for example, 802.11 packets from wiretap with
radio metadata always had "Wireshark generic radio metadata" even if the
metadata is part of the packet data - so that, for example, the pcap-common.c
code parsed the radiotap header and generated the "generic radio metadata" from
it - so that we could convert radiotap packets into packets for non-pcap/pcapng
file formats with different types of metadata, and convert those packets to
radiotap packets.

That would mean a radiotap packet would have both the "generic radio metadata"
and the radiotap header.

But file-pcap.c, file-pcapng.c, and dissectors for protocols such as rpcap
might then have to do the same stuff wiretap does.


You are receiving this mail because:
  • You are watching all bug changes.