Wireshark-commits: [Wireshark-commits] rev 45628: /trunk-1.8/wiretap/ /trunk-1.8/wiretap/: iseries.
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: guy@xxxxxxxxxxxxx
Date: Thu, 18 Oct 2012 05:23:03 GMT
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=45628

User: guy
Date: 2012/10/17 10:23 PM

Log:
 Copy over revisions from trunk:
 
   ------------------------------------------------------------------------
   r45627 | guy | 2012-10-17 22:20:09 -0700 (Wed, 17 Oct 2012) | 9 lines
 
   Handle the fractions-of-a-second part of the time stamp correctly. 
   Extract it as a string, not a number, and determine the resolution based
   on the length of the string, i.e. on the number of digits presented. 
   (If you base it on the numerical value, leading zeroes will not be taken
   into account, but they aren't any different from other digits when
   determining the resolution.)  The resolution is 1/10^ndigits seconds, so
   we have to multiply it by 10^(9-ndigits) to convert the number to
   nanoseconds.
 
   ------------------------------------------------------------------------
   r45626 | guy | 2012-10-17 21:52:33 -0700 (Wed, 17 Oct 2012) | 24 lines
 
   Redo the processing of lines in iSeries text packet dumps.
 
   Process several different flavors of header lines the same: "IP Header",
   "IPv6 Header", "ARP Header", "TCP Header", "UDP Header", "ICMP Header",
   "ICMPv6 Hdr", "Option Hdr" - the hex data for all of them should be
   included in the packet data.  Process continuation lines if those
   headers wrap over more than one line.
 
   Do not assume, or require, that *any* of those be present; there is no
   guarantee that "IP Header" or "IPv6 Header" will be present (there's at
   least one IBM page showing a packet with "ARP Header" in a trace), and
   there is no guarantee that "TCP Header" will be present (there are
   traces with "UDP Header" and "ICMPv6 Hdr").
 
   Do not impose limits, other than the overall line limit, on the amount
   of hex data in header or data lines; there is no guarantee that, for
   example, a TCP header is 20 bytes long (if there are TCP options, it
   *will* have more than 20 bytes).
 
   Make sure we have an even number of hex digits.
 
   Set "caplen" to the actual number of bytes we've read, even if that's
   less than the purported packet length.

Directory: /trunk-1.8/wiretap/
  Changes    Path          Action
  +245 -326  iseries.c     Modified