Wireshark-bugs: [Wireshark-bugs] [Bug 5164] New: when capture incudes pppoe header the rtp 2833
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5164
Summary: when capture incudes pppoe header the rtp 2833 will be
displayed as strange words
Product: Wireshark
Version: 1.4.0
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: sideslinder@xxxxxxxxx
Build Information:
Version 1.4.0 (SVN Rev 34005 from /trunk-1.4)
Copyright 1998-2010 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.16.6, (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, with PortAudio V19-devel (built
Aug
29 2010), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
as a cap file includes the pppoe header the rtp event 2833 will be wrongly
displayed with strange charactors. When display the flow of voip calls, the
graph will wrongly display the 2833 play load type information. I guess the
wireshark assumes the cap is ethernet packet, and goes the fixed offset to get
the 2833 playload type. Is it so?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
