Closed DONJAGA closed 2 years ago
The Wireshark dissector in this repository is for the Simple Message protocol only (ie: this protocol).
In the data you show, I see strings such as panda_link5
and panda_rightfinger
, which leads me to believe this is not a capture of Simple Message traffic -- as the Franka Emika Panda does not use Simple Message.
If this is a capture of TCPROS
or UDPROS
, you would need to use a different dissector.
As I don't believe there is anything wrong with the dissector in this repository, I'm going to close the issue.
We'll re-open if it turns out something does need to be fixed here.
Feel free to keep commenting on the issue of course.
Hello G.A. vd. Hoorn,
Thank you for your answer.
I am researching ROS-Security and correct me if I am wrong. I found that in the Franka documentation the communication uses "franka_msgs" which share similar elements to simple message structure.
As you stated that this dissector is only working with Simple Message Protocol and is there any way of enhancing this dissector to correlate with "franka_msgs"?
No, Simple Message and TCPROS
/UDPROS
are completely different.
Wireshark natively supports TCPROS
/UDPROS
, so you wouldn't need any .lua
dissectors.
Also:
I found that in the Franka documentation the communication uses "franka_msgs" which share similar elements to simple message structure.
As you stated that this dissector is only working with Simple Message Protocol and is there any way of enhancing this dissector to correlate with "franka_msgs"?
I'd suggest getting a little more familiar with how ROS works. franka_msgs
is not special, it's just a set of files containing IDL definitions of ROS messages which happen to encode data relevant for Franka Emika robots.
Also: ROS 1 has no security.
In the latest ROS noetic none of any TCP robotic arm communication packets are dissected by this Lua script.
Its looks like this