This is our old Q&A Site. Please post any new questions and answers at

Looking at the Display Filter Reference for Modbus/TCP I noticed that most of the fields are not supported in the newer Wireshark versions. I wonder why, and I'll be more than happy to understand how can I still use these fields

Many Thanks in advance,


asked 25 Jul '15, 05:35

ABK's gravatar image

accept rate: 0%

Which specific filters are no longer supported? (i.e., can you provide some of their filter names?)

(25 Jul '15, 07:05) Hadriel

I don't think they're gone - I think they just changed names and which protocol they're listed under.

I don't know anything about Modbus, but it looks like Wireshark added support for "Modbus RTU", as well as the previous "Modbus/TCP", so the display filter fields were split up: "Modbus/TCP" only lists the TCP-specific ones, "Modbus RTU" lists the RTU-specific ones, and a generic "Modbus" is where most of them are now, since they presumably apply to both TCP and RTU formats.

permanent link

answered 25 Jul '15, 07:19

Hadriel's gravatar image

accept rate: 18%

You are right thanks!! ABK

(25 Jul '15, 07:32) ABK

For reference, Modbus RTU is the binary protocol originally used over serial links that defines the basic data types and functions of Modbus, Modbus TCP is one of the variants of Modbus over IP that adds some header fields but doesn't alter the data types or functions used.

(25 Jul '15, 08:00) grahamb ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 25 Jul '15, 05:35

question was seen: 1,222 times

last updated: 25 Jul '15, 08:00

p​o​w​e​r​e​d by O​S​Q​A