On Sun, Jun 6, 2021 at 5:42 PM Jan Mall <jan.mall@xxxxxxxxxx> 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 find out on which bus (physical
> interface) I receive the traffic in order to perform dissection
> according to the message definitions for this bus. Of course the user
> could just change the network description in the plugins preferences
> every time he switches the interfaces, but I thought maybe there's a
> smoother solution.
Are the messages partitioned such that they are different on each
interface, or is it the case that Message 1 can appear on interface
types A and B but with different formats?
> On 07.06.21 02:24, Guy Harris wrote:
> > On Jun 6, 2021, at 5:13 PM, Jan Mall <jan.mall@xxxxxxxxxx> 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?
> > ___________________________________________________________________________
> > Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> > Archives: https://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)