https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2837
Summary: STUN protocol decodes from Client to Server not
recognised as STUN
Product: Wireshark
Version: 1.0.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: High
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: vk4gtw@xxxxxxxxxxx
Build Information:
Version 1.0.2 (SVN Rev 25698)
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.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 1, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap, from the PortableApps U3 device in drive E:.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
STUN client to server traffic (destination UDP port of 3478) not recognized as
STUN. Server reply traffic (from UDP port 3478) is recognized as STUN.
STUN client to server recognized as fragmented IP packet. See attached JPG.
Highlighted packet shown in decodes at bottom of screen. IP addresses incorrect
in top window.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.