[Roland Knall <rknall@xxxxxxxxx>]

Hi

Configuration is not passed during consecutive starts via the interface list, or if you start from the main-screen. But they are shared if you "restart" the capture. 

Currently I am in the process of writing the limitations down, to further down the road write a wiki-page containing all limitations. One more limitation is, that boolflags have to be at the end of the configuration list atm, if you intend to run a Python based extcap driver. Otherwise (as demonstrated by the example), the flag is passed with an extra space, which seems to crash the demo application for some reason. 

Also, "coming back" was not part of my original intention, but I agree, that some form of handling that should be implemented.

regards

Roland

On Fri, Oct 3, 2014 at 4:30 PM, <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.

 

Michael

___________________________________________________________________________
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