Ask Your Question

Wireshark 2.6 could not decode diameter messages

asked 2019-02-08 06:00:51 +0000

From wireshark version 2 and on, I could not decode diameter messages. Wireshark understand the packet as TCP Retransmission. Even with decode us it was not possible to decode it.

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2019-02-08 15:11:35 +0000

JeffMorriss gravatar image

Is the trace taken natively (e.g., with tcpdump or Wireshark) or was it created by some other method?

I suspect it was created by another method and whatever is creating the trace is putting fake TCP headers that don't have correct sequence numbers.

Regardless you should probably be able to avoid the problem by disabling the TCP preference for analyzing sequence numbers.

ps. if you open a bug please be sure to post a link to it here.

edit flag offensive delete link more

answered 2019-02-08 09:31:38 +0000

Anders gravatar image

Raise a bug report with a sample trace. It hard to speculate what the problem might be. Possibly duplicate messages you could try to filter those out with editcap.

edit flag offensive delete link more

Your Answer

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

Add Answer

Question Tools

1 follower


Asked: 2019-02-08 06:00:51 +0000

Seen: 890 times

Last updated: Feb 08 '19