Wireshark-bugs: [Wireshark-bugs] [Bug 5250] New: Add vendor identifier dissector access to BACne
Date: Wed, 22 Sep 2010 11:27:24 -0700 (PDT)

           Summary: Add vendor identifier dissector access to BACnet
                    Private Transfer Msgs
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]

Build Information:
TShark 1.5.0-SVN-ALC-092010

Copyright 1998-2010 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO

Compiled (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.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with
MIT Kerberos, with GeoIP.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version, based on libpcap version 1.0 branch 1_0_rel0b

Built using Microsoft Visual C++ 9.0 build 21022
BACnet has a private transfer service which is vendor specific.  The start of
each request and response contains the vendor identifier.  I've added a way for
vendors to provide their own dissectors by registering their vendor identifier.
 The packet-bacapp.c method fConfirmedPrivateTransfer has been modified to look
for a vendor specified dissector.  If found it will be run.  If not found we
default to running the standard dissection included in packet-bacapp.c.

I modified the summary column display for private transfer messages so that the
summary now displays the Vendor Identifier (V=xx) and the Service Number

I also removed 'static' from several useful BACnet methods and value_strings to
allow access in vendor specified dissectors.

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