ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Ethereal-dev: Re: [Ethereal-dev] interface options patch II

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Nathan Jennings <njen@xxxxxxxxxxxxx>
Date: Tue, 09 Sep 2003 22:45:45 -0400
Guy Harris wrote:

On Sep 9, 2003, at 9:33 AM, Graham Bloice wrote:
With your latest changes (patch III) the windows descriptions have been
removed in the Interface Options dialog, but IMHO this makes things much
more difficult as you only have the actual interface names to look at which,
as I mentioned previously, are not very helpful being strings such as
"\Device\Packet_{F30D9BC7-81C8-4FF1-B98E-DDE87A2DB765}" which are somewhat
hard to relate to actual NICS.

Thanks Graham for those screenshots... it's very helpful. (What? "{F30D9BC7-81C8-4FF1-B98E-DDE87A2DB765}" isn't obvious? ;o))

Just scrap the patch from "interface options patch III". (Although it should at least work correctly, even if it's difficult to make out which interface is which.) I never intended for the OS supplied description to be saved in the ethereal description string (only the matching device name).

There are at least a couple of options I see here:

1) have the description for a device, both in the drop-down list *and* in the default to the description from the OS, but let the user override it (in which case it's no longer available in either place, on the assumption that the user would have left intact whatever parts of the OS's description they considered useful):

2) have the description for a device in the drop-down list be the user-supplied description, if there is one, and otherwise use the OS's description, and in the list of interfaces in the "Interface Options" dialog box show both the OS's description *and* the user's description.

If no one objects, I'll work on a patch for option 2. (I'll probably include the default row size addition in a later patch.)

Thanks again for the help and suggestions. I hope 0.9.15 Windows users aren't too upset. :o( (I was hoping/trying to make it.)

-Nathan