Skip to content
Snippets Groups Projects
New look: Off

Propagate interface Comment field to the Capture... Interfaces dialogue box

    • Closed Issue created by Wireshark GitLab Migration @ws-gitlab-migration

    This issue was migrated from bug 3414 in our old bug tracker.

    Original bug information:

    Reporter: Stuart Kendrick
    Status: RESOLVED FIXED
    Product: Wireshark
    Component: GTK+ UI
    OS: All
    Platform: All
    Version: 1.0.7

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration
      Author

      :speech_balloon: Stuart Kendrick said:

      Build Information: Version 1.0.7 (SVN Rev 28014)

      Copyright 1998-2009 Gerald Combs <gerald@‍wireshark.org> 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.6.3, with Gcrypt 1.4.3, with MIT Kerberos, with PortAudio V19-devel, with AirPcap.

      Running on Windows Vista, build 6000, with WinPcap version 4.0.2 (packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without AirPcap.

      Built using Microsoft Visual C++ 6.0 build 8804

      I stuff NICs into PCs -- using multi-port cards, I can equip a PC with ~8-12 ports each.  Each interface plugs into a different point in my network.

The Capture, Interfaces command lists each interface but does so using a string which reflects the chip set beneath that port.

I propose propagating the Comment field from Preferences, Capture, Interfaces:Edit to this list.  I populate this field with site-specific strings (giving us enough information to figure out to which SPAN port on which Ethernet switch this interface attaches).

I realize that I can view this comment by clicking on Options.  But, in order to find the interface I want, I have to click on multiple Options buttons for multiple interfaces until I find the right one.  This is a tedious process.

If the Comment field were propagated to this dialogue box (Capture, Interfaces), then we could quickly select the interface of interest.
    • Wireshark GitLab Migration added enhancement uigtk version1.0 labels

      added enhancement uigtk version1.0 labels

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration
      Author

      :speech_balloon: Stig Bjørlykke said:

      A fix for this has been committed in revision 28482 for the upcoming 1.2 release. According to our documentation this should be the default behavior, so I will add this to the 1.0.9 queue, if we ever going to release another 1.0.

    • Wireshark GitLab Migration
      Wireshark GitLab Migration @ws-gitlab-migration
      Author

      :speech_balloon: Stig Bjørlykke said:

      *** Bug #3223 (closed) has been marked as a duplicate of this bug. ***

    • Wireshark GitLab Migration closed

      closed

    Please register or sign in to reply