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 2638] New: XOT PVC Setup reported as Invalid/short X.25 pa

Date: Tue, 24 Jun 2008 03:39:49 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2638

           Summary: XOT PVC Setup reported as Invalid/short X.25 packet
           Product: Wireshark
           Version: 0.99.6
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jon.goodchild@xxxxxxxxxxxxx


Build Information:
Version 0.99.6

Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.12.0, with GLib 2.14.1, with libpcap 0.9.7, with libz
1.2.3.3, with libpcre 7.4, without Net-SNMP, with ADNS, without Lua, with
GnuTLS
1.6.3, with Gcrypt 1.2.4, with MIT Kerberos, with PortAudio <= V18, without
AirPcap.

Running on Linux 2.6.22-14-generic, with libpcap version 0.9.7.

Built using gcc 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2).
--
When attempting to decode the following X.25 over TCP (XOT) packet (a PVC Setup
packet), it is reported as Invalid/short X.25 packet:

XOT header: 00 00 00 18
X.25 packet body: 10 00 f5 81 18 05 00 02 04 00 02 02 02 07 07 73 79 6e 63 30
78 6f 74 30

The X.25 packet is 24 octets long, so the length of 00 18 is correct.

Since the PVC Setup packet is not a normal X.25 packet (it's used only within
XOT), could it be that the decoding software for the X.25 packets does not cope
with it?


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