https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7374
--- Comment #18 from Michael Tüxen <tuexen@xxxxxxxxxxxxx> 2012-06-24 13:52:44 PDT ---
(In reply to comment #17)
> (In reply to comment #16)
> > > About the only other reason would be if, for example, the system weren't
> > > properly set up to allow dumpcap access to capture devices and you changed that
> > > while Wireshark was running - but that's also a rare operation.
> >
> > Which is exactly my main use case of updating the list of interfaces...
>
> Either it's still a rare operation or it isn't.
>
> If it is, then, as per Pontus' suggestion, it may not need more than a menu
> item.
>
> If it's not, that either means that
>
> 1) you're doing this to a lot of machines, but on any *given* machine it's
> only done once per machine
>
> or
>
> 2) somehow it doesn't "stick", and you have to do it multiple times per
> machine.
>
> If it's the former, is there a way to automate it? (For OS X, the current
> installer adds the startup item.)
>
> If it's the latter, why is it not sticking?
I do this once on a machine after reboot... (I don't use the installer on Mac
OS X and
don't install the startup item manually. On FreeBSD it depends if I'm
administrating
the machine or not...
So I'm fine as long as there is a way in the GUI to rescan the interfaces even
on
platforms where the automatic stuff is available.
Best regards
Michael
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
