Re: [Wireshark-users] Using wireshark to process my own capture file

Hi, Why not go for these: /* Reserved for private use. */ { 147, WTAP_ENCAP_USER0 }, { 148, WTAP_ENCAP_USER1 }, { 149, WTAP_ENCAP_USER2 }, { 150, WTAP_ENCAP_USER3 }, { 151, WTAP_ENCAP_USER4 }, { 1

[Wireshark-users] Using wireshark to process my own capture file

I have software-generated capture files of variable-length packets (my own, experimental, protocol) preceded by standard pcap headers. All of the header fields are correct. I will never have to process live data. There can never be anything unexpected in the file--really! In any case, what I