Hi all, since the commit for bug 1723 (done in revision 38679), I'm facing issues with text2pcap for really small packet dumps.
Let's take this simple file example: 0000 30 00 20 By executing the following command line: text2pcap.exe -q -l 162 temp.txt temp.pcap I get the following binary pcap file: 00000000: D4 C3 B2 A1 02 00 04 00 00 00 00 00 00 00 00 00 00000010: 00 90 01 00 A2 00 00 00 As you can see, the packet is not included in the pcap file and if I open it in Wireshark no packet is displayed. Adding explicit ASCII string (so as to follow more closely the usual text2pcap input format) after the bytes does not help either: 0000 30 00 20 ... When I use Wireshark version 38678, I get the following binary pcap: 00000000: D4 C3 B2 A1 02 00 04 00 00 00 00 00 00 00 00 00 00000010: 00 90 01 00 A2 00 00 00 7F 67 56 4E 00 00 00 00 00000020: 03 00 00 00 03 00 00 00 30 00 20 and everything works fine. I guess this is unexpected behavior and should be considered as a bug. Do you agree ? Unfortunately I do not have the time to look at the text2pcap.c changes right now, so any help is welcome. Regards, Pascal.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe