Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow extended filters #4

Open
tlnd opened this issue Jun 22, 2018 · 1 comment
Open

Allow extended filters #4

tlnd opened this issue Jun 22, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@tlnd
Copy link
Contributor

tlnd commented Jun 22, 2018

As tshark is used now, extended filter syntax can be used (tshark read filter). It should be allowed to pass an extended filter as option to the container in addition to the pcap filter. The pcap filter should always be applied for efficiency. The extended filter should only apply if given as argument.

@tlnd tlnd added the enhancement New feature or request label Jun 22, 2018
@wfailla
Copy link
Contributor

wfailla commented Jul 10, 2018

tshark does not allow for wireshark like filters to be applied to a capture stream. And the functionality of piping to a tshark and than applying a read filter is also broken (see https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2234) this feature will be placed on hold.

To use wireshark like filter syntax capture some files and use the tshark (provided in the docker-pcap container) to filter all packages in that file again:

-> % docker run --net=host -v $PWD/dump:/data --rm -ti travelping/pcap /bin/sh
/ # tshark -r /path/to/file -Y <filter>

The documentation will be updated soon to include this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants