Thanks for the hint with the interface_id - didn't knew that yet.
Mapping between interfaces and message definition files are done in the
preferences.
Good point with the capture files - listening for UI events wouldn't
work there. So probably I should stick with the solution of the
interfac
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_name(pinfo->epan,
> pinfo->rec->rec_header.packet_header.interface_id);"
Note that it is permitted to return NULL.
Note also that there is no guarantee that
pinf
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
Also are you running the same protocol on all the different buses, or has
each bus its own distinctive protocol?
cheers
Roland
Am Mo., 7. Juni 2021 um 02:58 Uhr schrieb Guy Harris :
> On Jun 6, 2021, at 5:41 PM, Jan Mall wrote:
>
> > The ultimate goal is an automotive dissector, which takes abs
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
