https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4506
--- Comment #1 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-02-19 08:38:05 CET ---
(In reply to comment #0)
> Build Information:
> Version 0.99.8 (SVN Rev 24492)
You should really try to use a more up to date version.
If you have private plugins demand an update from the supplier.
> Cannot capture anything but broadcast packets through a hub after attempting a
> capture at a customer site.
Are you 1000% sure it's a hub? Many so called hubs are actually switches in
disguise, see http://wiki.wireshark.org/HubReference
> Now all I can capture are broadcast traffic even in
> my home network.
Are you capturing in promiscuous mode? That's one of the capture options.
Another Windows XP computer loaded with the same versions (in
> this case 0.99.8)will capture all packets. The capture that also contains only
> broadcast traffic contains the following type of captures:
> "1 0.000000 96.16.49.83 192.168.1.104 TLSv1 Encrypted Alert" (I
> have attached the complete packet capture).
Than I assume your interface is 192.168.1.104, so you see your own traffic.
96.16.49.83 is from akamaitechnologies.com
> The other XP service pack 3 computer captures non broadcast traffic but does
> not contain any of the above packets going to and from 96.15.49.83.
That one probably has promiscuous capture enabled. and it doesn't have a link
up with Akamai Technologies.
> On the computer I having the problem with, I have done a system restore,
> deleted wireshark and winpcap but I still have the same problem. Also, another
> user at the same site also experienced the exact same problem.
That's probably also because the hub is no real hub.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
