Gary Taylor <squeaky@...> writes:
>
> I've got .pcap files that I use to verify traffic is
> bi-directional.
>
> I currently use tshark and do something like
> ./tshark -r capture.pcap ip.src == 192.168.1.1 | wc -l
> ./tshark -r capture.pcap ip.dst == 192.168.1.1 | wc -l
>
> and compare the number of lines returned. As long as they're
> close I'm happy.
>
> Is there a smarter method to compare ip "request/responses"?
> I don't need to have exact data. Just want to make sure the
> numbers are "close". I'd like do it one pass because the
> pcap files get rather large and can take a while to go
> through.
You could try looking at the various tshark -z options?
See https://www.wireshark.org/docs/man-pages/tshark.html
For example,
tshark -r capture.pcap -Y "ip.addr eq 192.168.1.1" -z conv,ip,"ip.src eq
192.168.1.1" -z conv,ip,"ip.dst eq 192.168.1.1" -q
or
tshark -r capture.pcap -Y "ip.addr eq 192.168.1.1" -z io,phs,"ip.src eq
192.168.1.1" -z io,phs,"ip.dst eq 192.168.1.1" -q
- Chris