Decoding Modbus TCP on different port number

asked 2020-05-04 11:29:34 +0000

Ramon de Vries
3 ●1 ●1 ●2

updated 2020-05-04 12:04:08 +0000

grahamb

flag of United Kingdom of Great Britain and Northern Ireland

23835 ●4 ●976 ●227 https://www.wireshark.org

Hi there,

great work developers and community for this great website. This has helped me numerous times in trouble shooting and learning the protocols etc.

I have a Question regarding Modbus/TCP. The default port is 502, but I have seen that some controllers can send Modbus TCP messages through a different portnumer, such as 503 for example. I have captured the these packets, but Wireshark does not decode these messages as Modbus. How can I tell/configure Wireshark to decode these messages as Modbus/TCP?

Many thanks

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2020-05-04 12:09:58 +0000

grahamb

23835 ●4 ●976 ●227 https://www.wireshark.org

Add an entry to the "Decode As..." table. This can be done by right-clicking a packet in the packet list that isn't being dissected correctly due to not being on port 502, choosing the option "Decode As..." and then adjusting the "Value" and "Current" fields as required. You can have as many entries as needed and can go directly to the table from the Analyze menu.

The table should look like this, I've added an entry for port 503.

image description

edit flag offensive delete link

Comments

Thanks for the information!

Ramon de Vries ( 2020-05-13 06:06:43 +0000 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2020-05-04 11:29:34 +0000

Seen: 4,571 times

Last updated: May 04 '20

Decoding Modbus TCP on different port number edit