--- Comment #19 from Pontus Fuchs <[email protected]> 2012-06-24 14:18:31 PDT ---
(In reply to comment #18)
> (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
> the machine or not...
> So I'm fine as long as there is a way in the GUI to rescan the interfaces even
> platforms where the automatic stuff is available.
Ok so I found that there is a refesh button. Not easy to find :)
capture options->manage interfaces->local interfaces
My patch does not touch this button. I don't see much point in moving it
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.