http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605
jay-wireshark@xxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jay-wireshark@xxxxxxxxxxxxx
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
Summary|No source and destination IP|Intermittent failure of IP
|address resolution |address resolution w/ADNS
Version|0.99.5 |0.99.7
------- Comment #4 from jay-wireshark@xxxxxxxxxxxxx 2007-12-23 14:36 GMT -------
I have what seems to be the same bug, but more details, so I'll reopen it.
This is happening when loading a dumpcap capture file.
With ADNS enabled, at least one problem is that Wireshark doesn't wait for the
responses before drawing the packet list - it's a little TOO async! So the
initial render will show mostly IP addresses.
A reload will, mostly, correct that. But I still see some IP addresses (e.g.
204.9.178.171 = blogs.sixapart.com) that should be able to be resolved, and no
number of reloads fixes that. Maybe it's overloading the name server (or the
link??), UDP packets are being dropped, and there's no retry in ADNS?
Turning off ADNS seems to be a workaround, but of course now it takes four
minutes to load a 16M capture :)
Do you want a capture of wireshark loading the capture, or is this enough info
to go on?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.