Wireshark-bugs: [Wireshark-bugs] [Bug 5487] New: "Displayed Columns" would benefit from a port n
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 10 Dec 2010 17:57:24 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5487

           Summary: "Displayed Columns" would benefit from a port number
                    option
           Product: Wireshark
           Version: 1.4.2
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: kfall@xxxxxxxxxxxxxxx


Build Information:
Version 1.4.2 (SVN Rev 34959 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 (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.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Nov
18 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.

--
When selecting View|"Displayed Columns", source and destination address can be
shown but port number (evidently) cannot.  For some traces (e.g., a localhost
transaction with 127.0.0.1 as both source and destination IP) where port
numbers are not otherwise displayed (e.g. TLS), it becomes confusing as to
which direction any given packet is headed.  This could be improved by allowing
the port number to appear as a column entry.  For packets lacking a port number
maybe "(none)" or "?" would be acceptable.

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