Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7514] New: ISDN LAPD X.31 packet traffic can not be decode

Date: Sun, 22 Jul 2012 10:28:42 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7514

           Summary: ISDN LAPD  X.31 packet traffic can not be decoded
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Dissection engine (libwireshark)
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: isdn@xxxxxxxxxxxxxx


Created attachment 8823
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8823
Example trace file for ISDN X.31 traffic

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
X.31 is X.25 over ISDN. It use SAPI 16 LAPD service. But it is not possible to
decode the I-frame data as X.25 with current wireshark versions, because if I
select the I-frame data section, the "Analyze as" menu item is grayed out.

I looked around the source code of the X25 protocol and modified the 
proto_reg_handoff_x25() function to also register to "lapd.sapi",
LAPD_SAPI_X25.
This did it for me, now the SAPI 16 I frames are decoded as X.25.
(see patch and example x31anno.trc file - is in EYEISDN format).

Only cosmetic issue is, that the protocol is still displayed as X.25 in the
protocol column - maybe somebody who knows more about the internals of
wireshark can register X.31 as second protocol type for X.25 and use it for
LAPD SAPI 16 traffic.

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