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 set capture device to none #196

Open
nshopik opened this issue Jun 20, 2017 · 4 comments
Open

Allow set capture device to none #196

nshopik opened this issue Jun 20, 2017 · 4 comments

Comments

@nshopik
Copy link
Contributor

@nshopik nshopik commented Jun 20, 2017

When capturing HEP packets usually its prefarable to disable listen on interface as you may get duplicate dialogs.

Currently there no way to set interface to none, only workaround set capture to loopback or read empty pcap

@nshopik
Copy link
Contributor Author

@nshopik nshopik commented Jun 20, 2017

On second though I think we should disable interface capture when HEP capture is enabled, to avoid false reports of double capture. As in most cases its not needed, but for these who need provide option to force capture on interface with HEP enabled

@Kaian
Copy link
Member

@Kaian Kaian commented Jun 20, 2017

Hi !

You mean when HEP is enabled in Listening mode, don't you?

If we implement the capture interface none it can be set as default in your sngreprc file (set capture.device none) so you can specify a capture interface whenever you want using -d command line option.

@nshopik
Copy link
Contributor Author

@nshopik nshopik commented Jun 20, 2017

Yeah I was talking about HEP listening mode.

none interface type is good solution but I merely suggest it to set to none if HEP enabled unless otherwise specified via command line or .sngreprc to avoid duplicates

@tomponline
Copy link

@tomponline tomponline commented Mar 7, 2019

This would be a great feature to have, as would it also allow you to run sngrep as non-root user as long as the HEP listen port was > 1024?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants