Comment # 14
on bug 12687
from Oliver Hartkopp
(In reply to Michael Mann from comment #12)
> I actually have a new patch that's a little better, but I was still using
> this conversation to refine it.
Can you share it?
> The original patch was intended mostly as a
> talking point to give you hints on where I was coming from to try to narrow
> the "language gap" we have when talking about the different technologies.
>
> Wireshark has no influence on the pcap file being written for capture,
> that's all in the vcan0 driver. You could set a byte in the CANFD structure
> (in the reserved fields) and that should show up in the Wireshark capture
> (undissected just like the current CANFD flag field).
> The socketCAN dissector could then look at that field to determine CANFD vs
> CAN. If we can agree on the value there, that I can put in an updated patch
> and you should get better results.
I suggested this bit to be set somewhere in Wiresharks data flow.
I don't see this flag being introduced into the Linux kernel as Wiresharks CAN
FD functionality would become Linux version dependent.
I still have a question about your perception of "that's all in the vcan0
driver".
Where can I find this "vcan0 driver"? Is it part of Wireshark?
How does Wireshark get the network traffic? Via netlink sockets?
You are receiving this mail because:
- You are watching all bug changes.
