Wireshark-bugs: [Wireshark-bugs] [Bug 2091] New: X25 reassembly when presenting out of order pac
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 11 Dec 2007 11:30:27 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2091

           Summary: X25 reassembly when presenting out of order packets
           Product: Wireshark
           Version: 0.99.6
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: gerhard.nospam@xxxxxxxxx
 BugsThisDependsOn: 2090


Build Information:
All versions - checked svn
Both WinXP and Solaris tested
--
Packets are supposed to arrive in order in X25. However packet presentation may
not be in order which causes Wireshark to present packets incorrectly.

An example, where X25 is transported in XOT where TCP segments may appear out
of order in Wireshark

(packet number from the test case)
e1. X25 packet 3 is received, with More bit set [presented OK]
e3. X25 packet 4 is received, with M=0 [presented OK]
e6. TCP retransmit of packet e1 (x25 packet 3, M=1)  [NOK, see below]
e11. X25 packet 5 M=0 [NOK]

Wireshark assumes that X25 packet 3 is preceding x25 packet 5 so packet e11
presents e6-e11 as a resembled X25 packet which is incorrect. The incorrect
assembly is propagated to next dissector as well.

The X25 reassembly should not process e3 at all, but I have failed to
understand how it should work.


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