For what it's worth, libpcap 1.8 and later don't require that a local interface
be openable before listing it in pcap_findalldevs(), so, whilst you might still
need dumpcap to *capture* packets, it should be possible to *enumerate*
interfaces directly within Wireshark/TShark with libpcap 1.8
:12
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Subject: Re: [Wireshark-dev] Compiling with or without extcap
I have 5 extcaps, and the difference is about half a second. Would be
interesting, what kind of devices you have in your extcap list.
But in general, I st
, elapsed time
> 3521000
>
> Regards
> Anders
>
> -Original Message-
> From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On
> Behalf Of Guy Harris
> Sent: den 8 januari 2018 02:46
> To: Developer support list for Wireshark <wireshark-dev@wireshark.
2018 02:46
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Subject: Re: [Wireshark-dev] Compiling with or without extcap
On Jan 7, 2018, at 3:19 PM, Roland Knall <rkn...@gmail.com> wrote:
> We had this discussion a bung of times. I have nothing
On Jan 7, 2018, at 3:19 PM, Roland Knall wrote:
> 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
>
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
On Sun, Jan 7, 2018 at 12:02 AM, Stig Bjørlykke wrote:
> On Sat, Jan 6, 2018 at 7:15 PM, Dario Lombardo <
> dario.lombardo...@gmail.com> wrote:
>
>> What about an environment variable that disable extcap interfaces loading?
>>
>
> Or even better; a UI configurable preference
On Sat, Jan 6, 2018 at 7:15 PM, Dario Lombardo
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
<anders.bro...@ericsson.com>
wrote:
>
>
>
>
> *From:* Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] *On
> Behalf Of *Dario Lombardo
> *Sent:* den 4 januari 2018 15:22
> *To:* Developer support list for Wireshark <wireshark-dev@wireshark.org>
> *
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of
Dario Lombardo
Sent: den 4 januari 2018 15:22
To: Developer support list for Wireshark <wireshark-dev@wireshark.org>
Subject: Re: [Wireshark-dev] Compiling with or without extcap
On Thu, Jan 4, 2018 at 3
Still, it looks for possible new extcap programs, which slows down the
systems a little bit I guess. But beside that, Dario is right, if you
disable all extcap, it behaves as if no extcap was present.
On Thu, Jan 4, 2018 at 3:21 PM, Dario Lombardo
wrote:
>
>
> On
On Thu, Jan 4, 2018 at 3:10 PM, Anders Broman
wrote:
> I don’t have a problem with making extcap a mandatory feature of
> Wireshark. But since extcap prolongs the startup time and clutters the
> interface list.
>
> I would like a feature to turn some or all extcap
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of
Dario Lombardo
Sent: den 4 januari 2018 13:41
To: Developer support list for Wireshark
Subject: [Wireshark-dev] Compiling with or without extcap
During some reviews it went out again the
13 matches
Mail list logo