Wireshark-bugs: [Wireshark-bugs] [Bug 11425] New: link layer type SLL (i.e. linux cooked capture
Date: Fri, 07 Aug 2015 12:37:26 +0000
Bug ID 11425
Summary link layer type SLL (i.e. linux cooked capture) is not detected in some cases
Product Wireshark
Version 1.12.6
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter tim_s.90@gmx.de

Build Information:
Version 1.12.6 (v1.12.6-0-gee1fce6 from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 17 2015),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
        Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, with 8073MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
I created an IP trace dump by listening on an Android phone's mobile data
interface using and old version of libpcap which someone ported to Android
(http://sourceforge.net/p/prueba-android/code/HEAD/tree/trunk/jni/).

The link layer type of the packets is SLL (i.e. linux cooked capture). The
captured SLL headers contain valid values according to
http://www.tcpdump.org/linktypes/LINKTYPE_LINUX_SLL.html. But when opening the
dump in Wireshark it misinterprets the link layer type as Ethernet II (and it
seems I can't even force Wireshark to interpret it as SLL).

The sample SLL capture file from https://wiki.wireshark.org/SLL is interpreted
and parsed correctly by wireshark. The only differences in the SLL header
between my captures and the sample are the fields: ARPHRD_ type, Link-layer
address length and Link-layer address.

See my capture: https://www.cloudshark.org/captures/45d86a8eea70


You are receiving this mail because:
  • You are watching all bug changes.