Wireshark Arnet/RDM/DMX dissector
Hey all,
I am currently updating the Wireshark Artnet dissector to better support RDM (over Artnet). The same time I created a DMX and RDM dissector. What I am now looking for are capture files of Artnet RDM traffic, to verify the dissectors. So if anybody out there is using Artnet I would be tankful if they could provide some capture files. - Erwin |
Thanks for doing this.
You can generate this traffic yourself using OLA (http://www.opendmx.net/index.php/OLA). Start up an instance on two hosts, patch the Dummy RDM responder to an ArtNet universe and use the web UI on the other instance to send RDM over ArtNet traffic. |
Ah interesting project, might have to add dissectors for the other supported protocols like sandnet and shownet too :-)
But I still would like to see some real world capture files from different kinds of devices. |
If you PM me the email address you want it to, I can send you some files...
|
1 Attachment(s)
Here is a wireshark capture of the traffic between AL's DMX Workshop and an Art-Net node. The Node has a single Lab-Pack RDM responder connected to the first port.
I hope this helps. Thanks for doing the Wireshark work, it's sorely needed. |
New test version of Wireshark with Artnet, RDM, DMX support. Windows 32bit only, if no big problems are found I will start pushing things upstream so it will end up in the official wireshark release.
http://downloads.erwinrol.com/Wiresh...-1.7.2-RDM.exe |
Hey all, the Wireshark team released a 1.8.0rc1 version. That version includes my latest Artnet/RDM work. So now ppl with OS/X can try it too. Just checkout the download page; http://www.wireshark.org/download.html
update: If you find bugs, let me know ASAP, so I can fix them before they release 1.8.0! - Erwin |
Hey, great, thank you for doing this work!
|
I tested 1.8.0rc1 on mac and can't find any problems. Thanks for this.
|
I'm testing/ using 1.8.0rc1. I think there are some things to do better:
First it doesn't support Artnet III ? Second thing is on an ArtTodRequest: It doesn't displays the command-byte correct (still there is only one command (0x00) yet) it should be known ans "TodFull" and not "unknown". I will further use it and report if I find (more) errors; It's much better then the old version, thanks ;) Greetings Methi |
Hi Erwin
I just spotted a small bug in the plugin. In this packet, our controller has sent a GET:SUB_DEVICE_REPORT_THRESHOLD to Subdevice 0, and the responder as responded with a NACK: Reason 0x0009 (SubDevice out of range) - the allowed range is 0x0001-0x0200. Wireshark has correctly determined the PDL of the Nack_Response packet as 2, but only takes the first byte before moving on to validate the checksum using the second half of the response. http://i571.photobucket.com/albums/s.../LabpackXT.png Hopefully a quick easy fix for you? Peter |
Anyway we can get this ported over to the draft E1.33? Would be very useful. Simon and I have already started laying out prototype implementations.
|
All times are GMT -6. The time now is 06:27 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.