Hi Roland,
> Could we additionally add a note to README.extcap? Just in case, some
> external extcap tools sumble across this as well?
I think there is no README.extcap. There is just extcap.adoc, but it is
about application, not about code/API. BTW I'm missing it.
Or do you think any other
This is almost certainly my fault when integrating extcap with wslog.
Thanks for looking into it.
I'm not sure disabling every message to stderr is a good idea. The
problem space is the same as with dumpcap and that already works seamlessly.
But for now muting stderr with extcap --debug is
Could we additionally add a note to README.extcap? Just in case, some
external extcap tools sumble across this as well?
Also, one more thing, have you tested with tshark only or also using qt? Qt
in general redirects all std... pipes, which should not matter as we are
started through dumpcap.
I'm ok with this change. I can give you direct support for the extcaps I
wrote (sshdump/ciscodump, udpdump, randpktdump), and do my best with the
others.
On Wed, Dec 1, 2021 at 2:18 PM Jirka Novak wrote:
> Hi,
>
> I noticed issue below and I propose a solution for it. Can I ask for
>
Hi,
I noticed issue below and I propose a solution for it. Can I ask for
comments?
Every extcap tool has --debug and --debug-file options, but when they
are used, it do "nothing". File is created, but it is empty.
Later I found that it must be used with --log-level=debug to really
log
