https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3228
Summary: SCTP Data Chunks are assumed to be M3UA if SCTP port is
2905, regardless of the PPID
Product: Wireshark
Version: 1.0.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: robm_campbell@xxxxxxxxxxx
Build Information:
Version 1.0.0
Copyright 1998-2008 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.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.5,
with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, without WinPcap, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
If the SCTP port in captured traffic is 2905 (the registered port for M3UA),
Data Chunks are decoded as M3UA even if the chunk Payload Protocol Indicator
(PPID) says otherwise e.g. setting the PPID to 16 correctly shows up as "DDP
Segment Chunk" but the chunk is still decoded as M3UA. If I then change the
SCTP port to say 7001 the PPID is still indicated as "DDP Segment Chunk" but
the chunk is then displayed simply as Data.
Data chunk decoding/dissection should depend on the PPID, not the port number.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.