Wireshark-bugs: [Wireshark-bugs] [Bug 3924] Network Name resolution with hosts files locks wires
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3924
--- Comment #3 from Chuck Bland <chuck@xxxxxxxxxxxxxx> 2009-10-22 15:06:18 PDT ---
Created an attachment (id=3824)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3824)
pcap file that shows the problem
Originally, I found this issue while teaching a class. The students install
Wireshark in the course of the class, so they are starting with a fresh
install.
Once we create a small (two entry) hosts file, WS is terminated and the file is
placed in the proper directory. WS is restarted and Network Layer Decoding is
enabled. When the attached file is opened, it appears WS locks up. I actually
believe that it is in some very hard and long loop trying to decode the
addresses.
This has happened with and without DNS deciding enabled.
If I wait long enough (sometimes as long as 40-60 minutes), a few (less than
10) lines will appear with the addresses decoded. From that point on, it
usually only takes a matter of 20-30 *seconds* to open and decode the file.
So it appears it takes testing on a fresh install in order to reproduce this
problem. This issue happens to all my students in the three classes I've
conducted this year.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
