Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version is a protocol to transmit data packets over a copper wire.

So is Ethernet. :-)

What you mean is " is a protocol to transmit data packets over "premises wiring including inside telephone wiring, coaxial cable, and power-line wiring", to quote G.9961.

Is their any plugin in wireshark to decode packets.

I don't know of any.


All packets that Wireshark can decode must be in some form of traffic capture file.

In what form are the packets? Are they encapsulated in some other protocol, or is, for example, G.9961 LLC the lowest-level protocol in those frames?

In the first case, any dissector would have to register itself with that other protocol, so as to see the packets. That would require knowing what the other protocol is, and how the frames encapsulated.

In the second case, either:

  • the traffic capture file format is an existing file format supported by Wireshark, in which case we would have to know how frames (as opposed to, for example, Ethernet or 802.11 or PPP or... frames) are indicated, and modify the code to read those files to indicate "this is a frame";

  • the traffic capture file format is a new format that Wireshark currently doesn't support, in which case we'd need a specification for that file format, so that we could add code to Wireshark to read those files, or, if no such specification is available, we would need several files of that format, and detailed dissections by some other program that reads those files of the files, so we can reverse-engineer it;

  • there isn't currently a file format that supports, in which case we would have to add support to the only file formats over which we have any control, namely pcap and pcapng, by adding a new link-layer header type, and then adding support for that in Wireshark.

Once that's done, a dissector for frames could be added.