t list for Wireshark
Sent: Sun, Nov 8, 2015 6:56 am
Subject: Re: [Wireshark-dev] CAN over Ethernet
When I say plain, maybe I should have said that I'm working at FPGA-level.
Basically, when I receive a CAN message, I put everything between
start-of-frame and end-of-frame in the Ethernet payloa
On Nov 8, 2015, at 3:56 AM, Kumquat KromKiller
wrote:
> When I say plain, maybe I should have said that I'm working at FPGA-level.
> Basically, when I receive a CAN message, I put everything between
> start-of-frame and end-of-frame in the Ethernet payload and since the length
> of the payloa
s no standard ethertype for this, you'll need to use Decode As to
> dissector and just register your dissector (handle) with the ethertype
> dissector table. (dissector_add_for_decode_as).
>
>
> -Original Message-
> From: Kumquat KromKiller
> To: Developer supp
type for this, you'll need to use Decode As to dissector and just
register your dissector (handle) with the ethertype dissector table.
(dissector_add_for_decode_as).
-Original Message-
From: Kumquat KromKiller
To: Developer support list for Wireshark
Sent: Sat, Nov 7, 2015
I choose how CAN messages will be transported, that is why I said I can add
whatever layers I want between Ethernet and CAN.
Right now, it's just plain encapsulation of CAN over Ethernet with a custom
EtherType greater than 0x0600.
Ideally, I would like to avoid making my own dissector. It would
Hi
It depends how the CAN messages are being transported within Ethernet. Then
you could write a dissector for the method, which in turn calls the CAN
dissector.
The same thing happens with a lot of other dissectors,the openSAFETY
disssector for instance.
regards,
Roland
On Sat, Nov 7, 2015 at
Hi everyone,
I need to transport CAN messages over Ethernet and I would like to be able
to dissect them in Wireshark for debugging purposes.
Considering the fact that I can add whatever layers I want between Ethernet
and CAN, what would be the most efficient way to achieve this ?
Thanks.
___
