Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 4780] New: text2pcap expects \n delimited text (instead of \r\n) on win32

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4780

           Summary: text2pcap expects \n delimited text (instead of \r\n)
                    on win32
           Product: Wireshark
           Version: 1.3.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Extras
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: yury@xxxxxxxxxx


Build Information:
http://media-2.cacetech.com/wireshark/win32/wireshark-win32-1.3.5.exe
--
I want to load HEX packets that I've typed in manually into Wireshark on win32.
To this end the following transformations are necessary if test.dat is a binary
file containing the packet data created with a suitable HEX editor (e.g. HxD):

od -Ax -tx1 -v test.dat > test.text
dos2unix test.text
text2pcap test.text test.pcap
wireshark test.pcap

The reason for this is that od from GnuWin32 (correctly) creates a HEX dump
where lines are delimited with \r\n as it should be by default on win32
platform. When this file is fed directly into text2pcap it takes only the first
line and disregards the rest of the file, effectively treating \r as EOF.

While this might be a correct behavior on Unix, this should not be the case on
win32 and is very confusing, because initially the user is confronted with
malformed packets without any clue on what's wrong as the very same commands
work correctly on Linux.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.