[mmann78@xxxxxxxxxxxx]

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 probably write a newer/simpler driver that exposed these bugs (i.e. translate Python example to C)

 

Note that while the example "provides" configuration, it doesn't actually pay attention to it "coming back" (like my driver needs).  Not sure if there is something special about how to launch a Python app (ie example provided) in Windows that would cause different "Window" behavior than a 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.

 

 

 

-----Original Message-----
From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Fri, Oct 3, 2014 10:40 am
Subject: Re: [Wireshark-dev] Extcap

On 3 October 2014 15:30, <mmann78@xxxxxxxxxxxx> 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 passed to it?

2. My extcap driver is a console executable that is not "hidden" and comes up over top of Wireshark while capturing (which is visually ugly).  Perhaps the Windows API used should be similar to dumpcap (CreateProcess instead of g_spawn_async).  It seems CreateProcess has the ability to hide dumpcap's console Window.

 

 

I wasn't sure if these were Bugs or Features and I needed to adapt my driver accordingly.  The overall functionality of Extcap is really nice though.

 

Are you planning to share (if possible) and document this somewhere, e.g. Wiki?

--

Graham Bloice

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