Wireshark-bugs: [Wireshark-bugs] [Bug 7712] Tshark not resolving names and not showing protocol
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 14 Sep 2012 14:45:54 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7712

Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff.morriss.ws@xxxxxxxxx

--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-09-14 14:45:54 PDT ---
What's interesting about the name resolution parts is that at the beginning of
the file 192.168.0.6 is not resolved:

www.google.ca,192.168.0.6,6

But towards the end, it is:

jstephens-mac.rim.net,www.google.ca,6

(That's the last frame and, yes, the PCAP file says that the source IP is
192.168.0.6.)

Do you have any of the asynchronous DNS options enabled?

(It should also be noted that the google.ca address is resolved very early on
in the file because packets 2 and 3 are a DNS lookup and response for that
name; Wireshark caches that knowledge so after that point in the file the
IP<->name mapping is known without Wireshark having to do an NS lookup.)

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