Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 7497] New: application incorrectly recognised by source port

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7497

           Summary: application incorrectly recognised by source port
           Product: Wireshark
           Version: 1.4.8
          Platform: x86
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Dissection engine (libwireshark)
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: white.gavin@xxxxxxxxx


Build Information:
Version 1.4.8 (SVN Rev 38094 from /trunk-1.4)

Compiled (32-bit) with GTK+ 2.16.6, 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.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jul
18 2011), with AirPcap.

Running on 32-bit Windows 7, build 7600, 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.10.3, Gcrypt 1.4.6, without AirPcap.


--
I have captured a number of FIX v5 sessions using tcpdump, and I am replaying
them with wireshark.

Typically, wireshark recognises the application as FIX and decodes the packets
correctly. 

However, where the source port is tcp/1433, wireshark fails to automatically
decode the traffic as FIX. Instead the packets show up as plan TCP with no
application decoding.

If I select the packet and click 'decode as.. fix', then the packets get
decoded correctly.

How to reproduce: capture a FIX session where the source port has been set to
tcp/1433 and open the capture file in wireshark.

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