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

Packetbeat - Cannot monitor ICMP by itself #757

Closed
andrewkroh opened this issue Jan 18, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@andrewkroh
Copy link
Member

commented Jan 18, 2016

Packetbeat won't start if you only enable ICMP in your config. The BPF string is malformed.

protocols:
   icmp:
     enabled: true
2016/01/18 17:15:14.033006 sniffer.go:251: DBG  BPF filter:  or icmp or icmp6
2016/01/18 17:15:14.033375 sniffer.go:130: DBG  Sniffer type: pcap device: any
2016/01/18 17:15:14.053315 packetbeat.go:182: CRIT Initializing sniffer failed: Error creating sniffer: syntax error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.