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

Feature Request: Blacklist interfaces and/or set a default interface #257

Closed
ipha opened this issue Aug 11, 2020 · 1 comment
Closed

Feature Request: Blacklist interfaces and/or set a default interface #257

ipha opened this issue Aug 11, 2020 · 1 comment
Milestone

Comments

@ipha
Copy link

ipha commented Aug 11, 2020

Is your feature request related to a problem? Please describe.
The auto-filled IP range always selects the "wrong" interface.
Between HyperV and VPNs, I frequently have 5+ interfaces active, most of which I never want to scan.
https://i.imgur.com/SggIKsA.png

Describe the solution you'd like
An option to blacklist certain interfaces so that VPN/VM interfaces don't show up in the interface list.

Describe alternatives you've considered
Maybe default to a physical interface instead of VPN/VM interfaces? Not sure if this is easy to detect though.

angryziber added a commit that referenced this issue Oct 27, 2020
…e order - Windows seems to return physical interfaces first
@angryziber angryziber added this to the 3.7.3 milestone Oct 27, 2020
@angryziber
Copy link
Collaborator

Detection on Windows has improved (preferring interfaces closer to the beginning of the list)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants