Yeah, I did that, I added a heuristic dissector table, and added
protoA and protoB to them.
Now wireshark always uses protoA to dissect (it should, because protoA
has no way to know that the packet is not for him [[it?]], because the
whole message space is covered by it). I also added protoB, and i
Akos Vandra writes:
> I would like to ask how does the Decode As... functionality work in wireshark?
> I have a CAN network, and on top of it there may be different
> higher-level protocols, depending on application.
> There is no identifier which would say that this belongs to protocol
> A, or p
Hi!
I would like to ask how does the Decode As... functionality work in wireshark?
I have a CAN network, and on top of it there may be different
higher-level protocols, depending on application.
There is no identifier which would say that this belongs to protocol
A, or protocol B.
I think the bes
