On Fri, Oct 3, 2014 at 10:16 PM, Tomasz Moń wrote:
> On Fri, Oct 3, 2014 at 5:17 PM, wrote:
>> Console App written in C(++) and not have the ugly console window pop up
>> when you start
>> capturing.
>>
>> If these are indeed "intended limitations", than yes documenting on the Wiki
>> would be
On Fri, Oct 3, 2014 at 5:17 PM, wrote:
> Console App written in C(++) and not have the ugly console window pop up when
> you start
> capturing.
>
> If these are indeed "intended limitations", than yes documenting on the Wiki
> would be a good start.
This is the way how it works in Windows.
If
Hi All,
I ran into trouble cross-compiling wirshark/tshak for ARM. It looks
like the same issues from
https://www.wireshark.org/lists/wireshark-users/200910/msg00121.html
and https://www.wireshark.org/lists/wireshark-dev/201104/msg00135.html :
Host-side tools (lemon) were being compiled with th
Unfortunately, I can't share the driver.
If these are "bugs", I can log them in bugzilla (as Extcap is now officially
part of the Wireshark source). I believe both issues could be tested with the
extcap example provided (extcap_example.py), although if someone asked/needed
it, I could proba
On 3 October 2014 15:30, wrote:
> I created an Extcap driver in Windows and noticed a few things:
>
> 1. Configuration is only passed if I launch interfaceSettings from opening
> Window. It is not saved or passed to driver every time. Is the driver
> supposed to save the last configuration pass
I created an Extcap driver in Windows and noticed a few things:
1. Configuration is only passed if I launch interfaceSettings from opening
Window. It is not saved or passed to driver every time. Is the driver
supposed to save the last configuration passed to it?
2. My extcap driver is a cons
