https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4372
--- Comment #10 from Gur Stavi <mister_great@xxxxxxxxx> 2010-03-14 08:20:59 PDT ---
> > Also since multiple clients may use winpcap at a given time, updating the list on the fly requires tricky synchronization logic.
>
> If there's an API provided to provoke WinPcap to recheck for interfaces, that
> would mean that multiple clients could call that API at a given time, so you'd
> still need the synchronization logic.
>
Not necessarily. It means that in systems where winpcap has only 1 client (I
guess that is 90+% of the systems) this API will succeed by simply clearing the
current list and recalling the initialization code. For systems with multiple
clients, which probably belong to expert users, it will fail and they will have
to fallback into manual restart of the service.
> > I asked them however to provide an API to refresh the list. For start it may even fail if there is an open winpcap client.
>
> If that's how they handle the synchronization problem, then the WinPcap calls
> to enumerate the interfaces could just call that routine and ignore its
> failure. Again, that hides that detail inside WinPcap, rather than requiring
> applications - Wireshark is not the only application that uses WinPcap - to be
> changed to use that routine.
They won't implement this interface for now for lack of resources.
So if I understand the situation correctly WinPcap (and as a result WireShark)
just won't support hot plugged network interfaces.
Since many WireShark users are not aware of WinPcap in the background, I hope
that you at least document this so they will know how to restart the WinPcap
service by themselves.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.