Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1605] Wireshark doesn't dynamically update the packet list

Date: Thu, 10 Apr 2008 02:20:00 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605





--- Comment #10 from Chris Maynard <christopher.maynard@xxxxxxxxx>  2008-04-10 02:19:57 GMT ---
OK, I don't have a problem with marking Bug #2437 as a duplicate of this one;
however, it's important to realize that the problem occurs with not only
network name resolution, but with both MAC name resolution and transport name
resolution as well.  And neither of those t require DNS queries to resolve.

And the behavior of turning on/off each one still confuses me.  For example,
with 3 columns displayed for MAC addresses - "Hardware src addr", "Hw src addr
(resolved)", and "Hw src addr (unresolved)" and with MAC name resolution
initially turned on, all 3 display the contents as expected; however, when you
disable MAC name resolution, all 3 columns now show the same contents, namely
unresolved hardware addresses.

So, either this is expected behavior and "Hardware src addr" really is the same
as "Hw src addr (resolved)" and Bug #2437 should be reopened since there is
duplication here, or the "Hw Src Addr (resolved)" column is behaving
incorrectly and should always resolve the name, independently of the name
resolution setting.

(Note that you must still select the "Hardware src addr" column after changing
the name resolution setting before the column contents is updated, and many
times this has to be done twice before it works.)

I repeated the above procedure for "Source port", "Src port (resolved)" and
"Src port (unresolved)", with the exact same results ... but with
enabling/disabling transport name resolution, of course.  And identical results
for the "Destination" counterparts as well.

I can't seem to get any network name resolution at all, but I suspect that it
would work similarly, so either "Network src addr" and "Net src addr
(resolved)" are the same and one should be eliminated (the ambiguous one), or
"Net src addr (resolved)" behavior should be corrected so that it always
resolves names independently of the name resolution setting.  For completeness,
the same goes for "Network dest addr" and "Net dest addr (resolved)", "Source
address" and "Src addr (resolved)", and finally, "Destination address" and
"Dest addr (resolved)".


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