Ask Your Question

Revision history [back]

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does. How can I show you the specific trace ? When I try to upload it here I get the message ">60 point required to upload files" ? Thanks, Alessandro

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does. How can does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I show you the specific trace ? When I try to upload it here I get the message ">60 point required to upload files" ? Thanks, Alessandrotried either with -2 or without

No Diameter is found.

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

No Diameter is found.

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

tshark -V -2 -r 333b.pcapng

No Diameter is found.

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

tshark -V -2 -r 333b.pcapng

No Diameter is found.

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

tshark -V -2 -r 333b.pcapng

No Diameter is found.

Whireshark Version 4.0.1 (v4.0.1-0-ge9f3970b1527).

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

tshark -V -2 -r 333b.pcapng

No Diameter is found.

Whireshark Version 4.0.1 (v4.0.1-0-ge9f3970b1527).

Check screenshot of decoded file:

https://www.dropbox.com/s/b8yeit4pz6lj6p4/Cattura.PNG?dl=0

Different output between tshark and wireshark

Hi, I was trying to match some diameter dialogues and I realized that tshark does not decode some packets while wireshark it does.

This is the file https://www.dropbox.com/s/msrsr9uwukd2anw/333b.pcapng?dl=0

I tried either with -2 or without

tshark -V -2 -r 333b.pcapng

No Diameter is found.

Whireshark Version 4.0.1 (v4.0.1-0-ge9f3970b1527).

Check screenshot of decoded file:

https://www.dropbox.com/s/b8yeit4pz6lj6p4/Cattura.PNG?dl=0

The wireshark configuration for Diameter protocol is:

Reassemble Diameter messages spanning multiple TCP segments -> flagged

TCP ports : 3000-3867,3869-3999

SCTP port(s) : 3868