https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15779
Bug ID: 15779
Summary: --ext-config --extcap-interface called twice when
opening extcap configuration dialog
Product: Wireshark
Version: 3.0.1
Hardware: x86
OS: All
Status: UNCONFIRMED
Severity: Normal
Priority: Low
Component: Extras
Assignee: bugzilla-ad...@wireshark.org
Reporter: wegwerf-1-...@gmx.de
Target Milestone: ---
Build Information:
Affects both Wireshark 3.0.x and 3.1.x.
--
When Wireshark starts and discovers network interfaces and extcaps, the usual
call sequence to an extcap offering a single interface is basically as follows:
1. foo --extcap-interfaces --extcap-version=3.x
--> foo then reports its interface "foobar"
2. foo --extcap-config --extcap-interface foobar
--> foo then reports foobar's configuration UI
3. foo --extcap-dlts --extcap-interface foobar
--> foo reports DLTS for its interface "foobar"
Now, when the user clicks on the gear icon next to the "foo: foobar"
extcap/network interface, my logging traces show that Wiresharks now calls the
configuration twice:
4. foo --extcap-config --extcap-interface foobar
5. foo --extcap-config --extcap-interface foobar
Only now the configuration UI is shown, and the user can interact with it.
Is this the intended behavior with Wireshark calling with "--extcap-config"
twice in a row before showing the extcap configuration UI?
In my case, my users are hit by a big performance penalty, as each invocation
of "--extcap-config" nees a roundtrip to an external service in order to
correctly populate some dynamic parts of the config UI.
Would it be possible for Wireshark to call only once, or is there something I
missed in understanding the need for calling "--exctcap-config" twice?
In a similar manner: what is the rationale for Wireshark calling a "full"
"--extcap-config" during startup without shown any configuration UI? In my
case, this is also a big startup penalty, as users have to wait for the extcap
to contact an external service, but the UI data isn't used at all at this time.
Would it be possible for Wireshark to signal different phases where
"--extcap-config" is used, so I can avoid costly external service contacts when
not really needed?
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
