On Jun 6, 2021, at 5:41 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 definitions,
So is there a single LIN
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
> definitions, I somehow need to fin
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
definitions, I somehow need to find out on which bus (physical
interface) I receive the
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* goal of this?
__
Hello together,
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. So I need to somehow get to know which interface
Wireshark is currently capturing on. I've checked the document
