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 5727] New: Wrong packet type association of SNMP trap afte

Date: Fri, 25 Feb 2011 05:10:16 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5727

           Summary: Wrong packet type association of SNMP trap after TFTP
                    transfer
           Product: Wireshark
           Version: 1.5.x (Experimental)
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: zefir.kurtisi@xxxxxxxxxxx


Created an attachment (id=5983)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5983)
Capture of wrongly assigned SNMP trap to previous TFTP session

Build Information:
Version 1.5.0 (SVN Rev 35637 from /trunk)

Copyright 1998-2011 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 (32-bit) with GTK+ 2.16.6, with GLib 2.24.2, 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
Jan
24 2011), 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.
--
Overview:
SNMP trap packet sent right after a successful TFTP transfer are wrongly
assigned to the previous TFTP session and interpreted as unknown TFTP opcode
packet type.

Test setup:
We are sending a configuration file to a embedded device over TFTP. Right after
the transfer a syslog message and a SNMP trap is send to the host.

In the setup we captured
 * the TFTP transfer goes between device:1025 and host:3293
 * the syslog between             device:1024 and host:514
 * the SNMP trap between          device:1025 and host:162

The SNMP trap is associated to the previous TFTP session, even if the
destination port differs.



Capture is attached.

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