Add CLI argument --adapter [<NAME>] to allow immediately starting the capture from a given network interface
#643
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…m a given interface
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new CLI argument
--adapter [<NAME>]to allow immediately starting the capture from a network interface given its name.If a name isn't passed to the
--adapterflag, the capture will be started from the latest sniffed adapter, or the default adapter in case it's the very first launch of the app.The same is done even in case the passed adapter name is invalid or not existing.
Since Sniffnet's CLI arguments are getting more complex, I decided to start using clap to parse them.
Fixes #636.