You cannot trace your code using prints because they're handled by the
caller (dumpcap). Have a look at the other extcaps for --debug and
--debug-file options to see how it's solved there.
On Wed, Jan 2, 2019, 17:40 hdv I actually found the issue(s), there were multiple issues stacked on top
> of
I actually found the issue(s), there were multiple issues stacked on top
of each other:
1) When using parameters and you fill in the default value in the dialog
before you start the capture, these parameters are not passed to the
extcap plugin. My assumption was that the parameters would always b
Hi folks,
I am currently working on S1G which brings with it Protocol Version 1.
I notice that the current code treats the Frame Control Field (FCF)
and duration as a separate top-level item and then adds a separate
top-level item (IEEE 802.11 Wireless LAN or IEEE 802.11 Wireless LAN
extension fr
