Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 43605: /trunk/ /trunk/doc/: rawshark
From: Jeff Morriss <[email protected]>
Date: Mon, 09 Jul 2012 10:01:41 -0400
[email protected] wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=43605

User: morriss
Date: 2012/07/07 06:31 PM

Log:
 First phase of fixing https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7380 :
Add a new name resolution option: whether or not use the configured (in the OS)
 name resolver (e.g., DNS) to resolve network names.  When this option is disabled
 but network name resolution is enabled then Wireshark will resolve only those
 names that it can from local sources.  This includes (at least, AFAIK):
- name resolutions that Wireshark picks up on from DNS packets it decodes
 - the "user hosts file" (~/.wireshark/hosts on *NIX)
 - what Wireshark reads out of capture file (the PCAPNG name resolution block)
This new preference defaults to "use external resolvers" for backward
 compatibility (so people turning on network name resolution will get the old
 behavior).
This option can be set via Edit->Preferences and on the command line; there
 remain several UIs (e.g., the "open capture file" dialog, the
 View->Name Resolution menu, etc.) that don't have the new option yet.
One place where this change is NOT backwards compatible is the "-Nn" 
option: previously this turned on (only) network name resolution.  Now 
it does the same but (since "N" isn't in the list of features enabled) 
external name resolvers won't be used.
I'm not horribly concerned about this, but I thought I'd mention it in 
case someone else thinks it's a bad thing.