osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Document why extcap utilities can't be run "by hand" on Windows 

Bug: 15591
Change-Id: Icb8246ba196df026736ce1e54eb2ace2c7cd49b0
Reviewed-on: https://code.wireshark.org/review/33530
Petri-Dish: Michael Mann <mmann78@netscape.net>
Tested-by: Petri Dish Buildbot
Reviewed-by: Anders Broman <a.broman58@gmail.com>
This commit is contained in:
Michael Mann 2019-06-09 08:06:00 -04:00 committed by Anders Broman
parent f93edf223b
commit 6476ec79aa
2 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/extcap.pod
View File

@ -29,13 +29,19 @@ called by the GUI in a row. In the following chapters we will refer to them as
"the extcaps".
Extcaps may be any binary or script within the extcap directory. Please note, that scripts
need to be executable without prefacing a script interpreter before the call. To go deeper
into the extcap utility development, please refer to README.extcap.
need to be executable without prefacing a script interpreter before the call.
WINDOWS USER: Because of restrictions directly calling the script may not always work.
In such a case, a batch file may be provided, which then in turn executes the script. Please
refer to doc/extcap_example.py for more information.
When Wireshark launches an extcap, it automatically adds its installation path
(c:\Program Files\Wireshark\) to the DLL search path so that the extcap library dependencies
can be found (it is not designed to be launched by hand). This is done on purpose. There should
only be extcap programs (executable, python scripts, ...) in the extcap folder to reduce the startup
time and not have Wireshark trying to execute other file types.
=head1 GRAMMAR ELEMENTS
Grammar elements:

6
docbook/wsdg_src/WSDG_chapter_capture.adoc
View File

@ -71,6 +71,12 @@ IMPORTANT: *Windows Users* Because of restrictions directly calling the script m
In such a case, a batch file may be provided, which then in turn executes the script.
Please refer to <<ChCaptureExtcapWindowsShell>> for more information.
When Wireshark launches an extcap, it automatically adds its installation path
(c:\Program Files\Wireshark\) to the DLL search path so that the extcap library dependencies
can be found (it is not designed to be launched by hand). This is done on purpose. There should
only be extcap programs (executable, python scripts, ...) in the extcap folder to reduce the startup
time and not have Wireshark trying to execute other file types.
[[ChCaptureExtcapProcess]]
==== Extcap command line interface