Wireshark-bugs: [Wireshark-bugs] [Bug 4803] New: Capture from named pipes fails for some data li
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4803

           Summary: Capture from named pipes fails for some data link
                    types.
           Product: Wireshark
           Version: 1.2.8
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Build Information:
Version 1.2.8 (SVN Rev 32676)

Copyright 1998-2010 Gerald Combs <[email protected]> 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 with GTK+ 2.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5,
with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built May  5 2010),
with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.

--
When we start Wireshark with -i option to capture from a named pipe, if we set
the data link type as Ethernet(1) or MTP2_WITH_PHDR(139), everything is OK and
it works. But if we set the data link type to something like LAPD(181), the
pipe does not work and Wireshark does not capture anything.
I think the pipe mechanism works for some data link types and fails for some
others.

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