At 17:46 07.06.2023, you wrote:
>I don't know why I'm not receiving all messages on this thread, but I'm unable
>to respond to the latest one from Guy, so I'm responding to this one instead.
>
>In any case, here's a simple proof-of-concept in Lua using the "Decode As"
>solution referenced below:
quot;can.subdissector"):add_for_decode_as(p_cansub)
Hope it helps,
Chris
> -----Original Message-
> From: Wireshark-users On
> Behalf Of Fabian Cenedese
> Sent: Monday, June 5, 2023 4:58 PM
> To: Community support list for Wireshark us...@wireshark.org>
> Subje
On Jun 5, 2023, at 1:58 PM, Fabian Cenedese wrote:
> At 22:29 05.06.2023, Guy Harris wrote:
>
>> On Jun 5, 2023, at 3:43 AM, Fabian Cenedese wrote:
>>
>>> We're using CAN bus as protocol and I implemented a capture
>>> to save the sent and received frames into a .pcapng file.
>>
>> So presuma
At 22:29 05.06.2023, Guy Harris wrote:
>On Jun 5, 2023, at 3:43 AM, Fabian Cenedese wrote:
>
>> We're using CAN bus as protocol and I implemented a capture
>> to save the sent and received frames into a .pcapng file.
>
>So presumably that's using LINKTYPE_CAN_SOCKETCAN as the link-layer type in
On Jun 5, 2023, at 3:43 AM, Fabian Cenedese wrote:
> We're using CAN bus as protocol and I implemented a capture
> to save the sent and received frames into a .pcapng file.
So presumably that's using LINKTYPE_CAN_SOCKETCAN as the link-layer type in the
IDBs, with the SocketCAN pseudo-header:
Hello
We're using CAN bus as protocol and I implemented a capture
to save the sent and received frames into a .pcapng file. I can
load it in Wireshark and the frames are displayed as CAN which
is correct. However the fields are only shown as identifier and
data bytes which doesn't say much yet.
I
