ion of the
interface_id and if this is not available, force the user to explicitly
specify which message definitions to use.
On 07.06.21 18:32, Guy Harris wrote:
On Jun 7, 2021, at 4:15 AM, Jan Mall wrote:
After continuing searching I found this snippet in the UI part:
"epan_get_interface_n
On 07.06.21 02:41, Richard Sharpe wrote:
On Sun, Jun 6, 2021 at 5:42 PM Jan Mall wrote:
The ultimate goal is an automotive dissector, which takes abstract
network descriptions for automotive buses and dissects the messages on
the bus accordingly. But as every bus has a different set of message
, Guy Harris wrote:
On Jun 6, 2021, at 5:13 PM, Jan Mall wrote:
I'm currently developing a plugin/dissector (C API), which should have a
different dissection behavior depending on the interface Wireshark is currently
listening on.
Why?
What is the *ultimate* go
a hint or a direction where to look at. Would
help me a lot.
Thanks & Greets
Jan Mall
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www
