[Roland Knall <rknall@xxxxxxxxx>]

We had this discussion a bung of times. I have nothing against having a preference, but I am very much against making not-loading extcap the default. New users should not face a hassle to enable a capture interface, but existing users, who wish to improve the performance in any way, can profit from an option doing exactly that.

So +1 on making this option available big -1 on making it default to not-loading

cheers

On Sun, Jan 7, 2018 at 10:21 PM, Dario Lombardo <dario.lombardo.ml@xxxxxxxxx> wrote:

On Sun, Jan 7, 2018 at 12:02 AM, Stig Bjørlykke <stig@xxxxxxxxxxxxx> wrote:

On Sat, Jan 6, 2018 at 7:15 PM, Dario Lombardo <dario.lombardo.ml@xxxxxxxxx> wrote:

What about an environment variable that disable extcap interfaces loading?

Or even better; a UI configurable preference to enable/disable extcap interfaces.

This should be default on.  When turned on or off it will automatically run a "Refresh Interfaces" to load/unload extcap interfaces without having to manually restart or "Refresh Interfaces".

Sounds good!

I'm working on 3 separate patches:

1) remove extcap ifdefs

2) prevent extcap loading based on env variable (during the review process we can decide whether to keep this or not)

3) prevent extcap loading based on pref.

For the last one I'm just missing how to properly refresh the interface list. I've called wsApp->refreshLocalInterfaces() but the list doesn't get refreshed. Can you give it a look?

Thanks.

Dario. 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe