 | 1 | initial version |
The link you point to is the "services" file that Wireshark uses to translate between TCP and UDP port numbers and protocol names. That's a file, in the UNX "services" file format, generated from the IANA Service Name and Transport Protocol Port Number Registry; the appearance of a port number and associated protocol in that file does NOT* indicate that Wireshark supports dissecting the protocol in question.
And, in fact, the only file anywhere in the Wireshark source that mentions ArcLink is the services file; there is no support for dissecting the protocol.
A search for "ArcLink over Ethernet" pops up a bunch of hits about "ArcLink", from Lincoln Electric, for welding equipment (presumably "Arc" as in "arc welding"). A search for "ArcLink over tcp" popped up references both to Lincoln Electric's ArcLink and what I presume is an unrelated protocol for seismic data. The IANA registry indicates that the entry in question refers to Lincoln Electric's protocol.
In order to implement support for ArcLink in Wireshark, we would need a specification for ArcLink.
