Ask Your Question
0

tshark does not filter packets inside docker container

asked 2020-03-19 11:34:25 +0000

Abhi gravatar image

We have a situation where tshark command runs fine and filters a pcap file. But the same command fails to run within the docker container running in kubernetes.

Here is the command in question.

tshark -n -r input.pcap -w output.pcap -Y "diameter.Bearer-Identifier == 05"

Details CentOS Linux release 7.5.1804 (Core) tcpdump version 4.9.2 libpcap version 1.5.3 OpenSSL 1.0.2k-fips 26 Jan 2017 TShark 1.10.14 (Git Rev Unknown from unknown)

Please respond if any one has faced similar situation.

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2020-03-20 12:17:59 +0000

Abhi gravatar image

Found the root cause of this problem. Inside the container the diameter agent was running on a non default port. Hence it wasn't filtering the files. The version of tshark wasn't an issue.

tshark -d tcp.port==<your-port>,diameter -n -r input.pcap -w output.pcap -Y "diameter.Bearer-Identifier == 05"

edit flag offensive delete link more
0

answered 2020-03-19 12:15:54 +0000

grahamb gravatar image

The version of tshark (1.10.14) you're running is too old.

As you can see from the Wireshark Display Filter field reference the field diameter.Bearer-Identifier was only introduced in 1.2.2

edit flag offensive delete link more

Comments

The AVP is defined in the dictionary.xml and it works outside the container. When we run the same command inside docker it does not filter it out!

Abhi gravatar imageAbhi ( 2020-03-20 03:37:49 +0000 )edit

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

Stats

Asked: 2020-03-19 11:34:25 +0000

Seen: 197 times

Last updated: Mar 20