[bugzilla-daemon@xxxxxxxxxxxxx]

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1836

           Summary: Text2pcap doesn't handle timestamp starting with 00:
           Product: Wireshark
           Version: 0.99.6
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: mike@xxxxxxxxxxxxxx


Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Text2pcap doesn't handle timestamp starting with 00: (12am) correctly.

Example:
Timestamp in %H:%M:%S. format for the two following frames are ignored by
text2pcap
00:15:14.0005
000000 45 00 00 34 89 D4 40 00 80 06 6D 78 08 08 07 36 C0 A8 33 91 0A 64 00 15
CA 50 18 B6 00 00 00 00 80 02 FA F0 83 30 00 00 02 04 05 B4 01 03 03 00 01 01
04 02 

00:15:14.0007
000000 45 00 00 34 77 C7 40 00 80 06 7F 85 C0 A8 33 91 08 08 07 36 00 15 0A 64
33 C1 D7 A0 CA 50 18 B7 80 12 44 70 2E 3E 00 00 02 04 05 B4 01 03 03 00 01 01
04 02 

But timestamps as the following ones are correctly handled:
10:15:14.0005
000000 45 00 00 34 89 D4 40 00 80 06 6D 78 08 08 07 36 C0 A8 33 91 0A 64 00 15
CA 50 18 B6 00 00 00 00 80 02 FA F0 83 30 00 00 02 04 05 B4 01 03 03 00 01 01
04 02 

10:15:14.0007
000000 45 00 00 34 77 C7 40 00 80 06 7F 85 C0 A8 33 91 08 08 07 36 00 15 0A 64
33 C1 D7 A0 CA 50 18 B7 80 12 44 70 2E 3E 00 00 02 04 05 B4 01 03 03 00 01 01
04 02 

So difference between working and non working frames is just timestamp hour.
For timestamp starting with 00: text2pcap just ignored it.
For timestamp that doesn't start with 00: it is ok.

Proposal is either to update text2pcap documentation or to describe such
limitation, either to correct such behavior.


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