Wireshark · Wireshark-dev: Re: [Wireshark-dev] Wireshark-dev Digest, Vol 86, Issue 20

["Turney, Cal" <cal.turney@xxxxxxx>]

On Jul 10, 2013, at 10:09 AM, "Turney, Cal" <cal.turney@xxxxxxx> wrote:

>> The patch for Bug 8808 causes a console warning to be displayed if the snaplen (wth->snapshot_length) in the global header of the capture file does not match the packet size (hdr->hdr.incl_len).  We are seeing thousands of "File has packet larger than file's snapshot length." warnings because of a bug in our company's hybrid tcpdump app used for capturing traffic directly on the customer's NAS equipment.  The snaplen option of the app is functional but it hard-codes a snaplen of 1516 in the global header.

>So is this on non-Ethernet hardware that has a maximum packet length > 1516, is it on Ethernet hardware doing jumbo frames, or is it on Ethernet hardware where the captured data includes the FCS (hence 1518 bytes)?

It is on Ethernet jumbo-capable Intel, Broadcom, and some others.  It looks like the original tcpdump developer hard-coded 1516 when he probably meant 1514.

>>  This bug has been around for at least five years and possibly forever.
>>
>> Just curious.  Does anyone know of an app that uses or pays attention to the global snaplen value?  Wireshark prior to r49999, UN!X tcpdump, and MS Netmon do not.

> tcpdump/WinDump use libpcap/WinPcap to read capture files, and the pcap-reading code in libpcap/WinPcap does some hacks to work around an old ("old" as in "2.3") Solaris bug and ends up throwing out whatever packet data goes past the global snaplen.

> There might also be other libpcap/WinPcap-based applications that take the snaplen seriously and allocate buffers of that length and don't just treat the snaplen as a hint and grow the buffer as needed (hopefully, they don't do something careless such as *assuming* no packet will be bigger than that, and, instead, either report an error).

>> The bug in our code will be fixed but our customers are very slow to upgrade their software so we will continue to see these warnings for at least two years.  Would anyone object to my adding an option in Preferences>Protocols>Frame to ignore these mismatches but set the default to NOT ignore them?

> Well, libwiretap doesn't bother trying to deal with the Solaris 2.3 bug in question, so I'm not sure there's any harm in not bothering to report the problem and just returning the entire packet.

Are you saying that rather than adding an option to ignore snapshot_length/packet size discrepancies it might be best to not generate these warnings?

------------------------------

Message: 2
Date: Fri, 12 Jul 2013 08:04:36 +0200
From: Fabio Tarabelloni <fabio.tarabelloni@xxxxxxxx>
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] New updated version info
Message-ID:
        <CADQS9717SmvM=bCOYpkq4cQ_BHwcWtjndDQzkL_zU0e2ZJU_kw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi,

I wrote in order to ask when current trunk wireshark version will be enable in *Development Release* download section.

Thanks
Fabio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20130712/008ecbc4/attachment.html>

------------------------------

Message: 3
Date: Fri, 12 Jul 2013 10:28:17 +0100
From: Jo?o Amaral <jpgamaral@xxxxxxxxx>
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev]  Installing SVN 50510
Message-ID: <03926961312E4E319348BC825A0B8613@xxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hello,

I'm trying to compile SVN 50510. After running ./configure --with-gtk2 --enable-setuid-install I get no errors, but running make I get the following output:


> codecs/Makefile.am:28: library used but `RANLIB' is undefined
> codecs/Makefile.am:28:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
> codecs/Makefile.am:28:   to `configure.ac' and run `autoconf' again.
> echld/Makefile.am:34: Libtool library used but `LIBTOOL' is undefined
> echld/Makefile.am:34:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> echld/Makefile.am:34:   to `configure.ac' and run `aclocal' and `autoconf' again.
> echld/Makefile.am:34:   If `LT_INIT' is in `configure.ac', make sure
> echld/Makefile.am:34:   its definition is in aclocal's search path.
> epan/Makefile.am:57: Libtool library used but `LIBTOOL' is undefined
> epan/Makefile.am:57:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/Makefile.am:57:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/Makefile.am:57:   If `LT_INIT' is in `configure.ac', make sure
> epan/Makefile.am:57:   its definition is in aclocal's search path.
> epan/crypt/Makefile.am:34: Libtool library used but `LIBTOOL' is undefined
> epan/crypt/Makefile.am:34:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/crypt/Makefile.am:34:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/crypt/Makefile.am:34:   If `LT_INIT' is in `configure.ac', make sure
> epan/crypt/Makefile.am:34:   its definition is in aclocal's search path.
> epan/dfilter/Makefile.am:32: Libtool library used but `LIBTOOL' is undefined
> epan/dfilter/Makefile.am:32:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/dfilter/Makefile.am:32:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/dfilter/Makefile.am:32:   If `LT_INIT' is in `configure.ac', make sure
> epan/dfilter/Makefile.am:32:   its definition is in aclocal's search path.
> epan/dissectors/Makefile.am:23: Libtool library used but `LIBTOOL' is undefined
> epan/dissectors/Makefile.am:23:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/dissectors/Makefile.am:23:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/dissectors/Makefile.am:23:   If `LT_INIT' is in `configure.ac', make sure
> epan/dissectors/Makefile.am:23:   its definition is in aclocal's search path.
> epan/ftypes/Makefile.am:29: Libtool library used but `LIBTOOL' is undefined
> epan/ftypes/Makefile.am:29:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/ftypes/Makefile.am:29:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/ftypes/Makefile.am:29:   If `LT_INIT' is in `configure.ac', make sure
> epan/ftypes/Makefile.am:29:   its definition is in aclocal's search path.
> epan/wmem/Makefile.am:34: Libtool library used but `LIBTOOL' is undefined
> epan/wmem/Makefile.am:34:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/wmem/Makefile.am:34:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/wmem/Makefile.am:34:   If `LT_INIT' is in `configure.ac', make sure
> epan/wmem/Makefile.am:34:   its definition is in aclocal's search path.
> epan/wslua/Makefile.am:30: Libtool library used but `LIBTOOL' is undefined
> epan/wslua/Makefile.am:30:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/wslua/Makefile.am:30:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/wslua/Makefile.am:30:   If `LT_INIT' is in `configure.ac', make sure
> epan/wslua/Makefile.am:30:   its definition is in aclocal's search path.
> epan/wspython/Makefile.am:29: Libtool library used but `LIBTOOL' is undefined
> epan/wspython/Makefile.am:29:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> epan/wspython/Makefile.am:29:   to `configure.ac' and run `aclocal' and `autoconf' again.
> epan/wspython/Makefile.am:29:   If `LT_INIT' is in `configure.ac', make sure
> epan/wspython/Makefile.am:29:   its definition is in aclocal's search path.
> plugins/asn1/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/asn1/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/asn1/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/asn1/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/asn1/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/docsis/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/docsis/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/docsis/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/docsis/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/docsis/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/ethercat/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/ethercat/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/ethercat/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/ethercat/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/ethercat/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/gryphon/Makefile.am:39: Libtool library used but `LIBTOOL' is undefined
> plugins/gryphon/Makefile.am:39:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/gryphon/Makefile.am:39:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/gryphon/Makefile.am:39:   If `LT_INIT' is in `configure.ac', make sure
> plugins/gryphon/Makefile.am:39:   its definition is in aclocal's search path.
> plugins/irda/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/irda/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/irda/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/irda/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/irda/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/m2m/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/m2m/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/m2m/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/m2m/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/m2m/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/mate/Makefile.am:40: Libtool library used but `LIBTOOL' is undefined
> plugins/mate/Makefile.am:40:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/mate/Makefile.am:40:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/mate/Makefile.am:40:   If `LT_INIT' is in `configure.ac', make sure
> plugins/mate/Makefile.am:40:   its definition is in aclocal's search path.
> plugins/opcua/Makefile.am:38: Libtool library used but `LIBTOOL' is undefined
> plugins/opcua/Makefile.am:38:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/opcua/Makefile.am:38:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/opcua/Makefile.am:38:   If `LT_INIT' is in `configure.ac', make sure
> plugins/opcua/Makefile.am:38:   its definition is in aclocal's search path.
> plugins/profinet/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/profinet/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/profinet/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/profinet/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/profinet/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/stats_tree/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/stats_tree/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/stats_tree/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/stats_tree/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/stats_tree/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/unistim/Makefile.am:38: Libtool library used but `LIBTOOL' is undefined
> plugins/unistim/Makefile.am:38:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/unistim/Makefile.am:38:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/unistim/Makefile.am:38:   If `LT_INIT' is in `configure.ac', make sure
> plugins/unistim/Makefile.am:38:   its definition is in aclocal's search path.
> plugins/wimax/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/wimax/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/wimax/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/wimax/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/wimax/Makefile.am:37:   its definition is in aclocal's search path.
> plugins/wimaxasncp/Makefile.am:40: Libtool library used but `LIBTOOL' is undefined
> plugins/wimaxasncp/Makefile.am:40:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/wimaxasncp/Makefile.am:40:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/wimaxasncp/Makefile.am:40:   If `LT_INIT' is in `configure.ac', make sure
> plugins/wimaxasncp/Makefile.am:40:   its definition is in aclocal's search path.
> plugins/wimaxmacphy/Makefile.am:37: Libtool library used but `LIBTOOL' is undefined
> plugins/wimaxmacphy/Makefile.am:37:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> plugins/wimaxmacphy/Makefile.am:37:   to `configure.ac' and run `aclocal' and `autoconf' again.
> plugins/wimaxmacphy/Makefile.am:37:   If `LT_INIT' is in `configure.ac', make sure
> plugins/wimaxmacphy/Makefile.am:37:   its definition is in aclocal's search path.
> ui/Makefile.am:32: library used but `RANLIB' is undefined
> ui/Makefile.am:32:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
> ui/Makefile.am:32:   to `configure.ac' and run `autoconf' again.
> ui/cli/Makefile.am:31: library used but `RANLIB' is undefined
> ui/cli/Makefile.am:31:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
> ui/cli/Makefile.am:31:   to `configure.ac' and run `autoconf' again.
> ui/gtk/Makefile.am:31: library used but `RANLIB' is undefined
> ui/gtk/Makefile.am:31:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
> ui/gtk/Makefile.am:31:   to `configure.ac' and run `autoconf' again.
> ui/qt/Makefile.am:31: library used but `RANLIB' is undefined
> ui/qt/Makefile.am:31:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
> ui/qt/Makefile.am:31:   to `configure.ac' and run `autoconf' again.
> wiretap/Makefile.am:31: Libtool library used but `LIBTOOL' is undefined
> wiretap/Makefile.am:31:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> wiretap/Makefile.am:31:   to `configure.ac' and run `aclocal' and `autoconf' again.
> wiretap/Makefile.am:31:   If `LT_INIT' is in `configure.ac', make sure
> wiretap/Makefile.am:31:   its definition is in aclocal's search path.
> wsutil/Makefile.am:63: Libtool library used but `LIBTOOL' is undefined
> wsutil/Makefile.am:63:   The usual way to define `LIBTOOL' is to add `LT_INIT'
> wsutil/Makefile.am:63:   to `configure.ac' and run `aclocal' and `autoconf' again.
> wsutil/Makefile.am:63:   If `LT_INIT' is in `configure.ac', make sure
> wsutil/Makefile.am:63:   its definition is in aclocal's search path.
> make: *** [Makefile.in] Error 1
>
>

I have already installed successfully version SVN 50460. I'm guessing there is some problem with libtool?
I'm using Ubuntu 13.04 virtualised on VMware Fusion 5.0.3.

Thanks.
Jo?o

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20130712/5cdeea8d/attachment.html>

------------------------------

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev


End of Wireshark-dev Digest, Vol 86, Issue 20
*********************************************