Accept pf_ring or pfring in Packetbeat configuration #671
Conversation
This file contains 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
The documentation says to use pf_ring but the code accepts pfring only.
andrewkroh
force-pushed
the
bugfix/pf_ring
branch
from
c813393
to
e2f1e8a
Compare
|
LGTM. |
tsg
added a commit
that referenced
this pull request
Jan 10, 2016
Accept pf_ring or pfring in Packetbeat configuration
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.
The documentation says to use
type: pf_ringbut the code only acceptstype: pfring. This change allows the code to accept eitherpfringorpf_ring(to not break existing config).packetbeat.go:202: CRIT Initializing sniffer failed: Error creating sniffer: Unknown sniffer type: pf_ring