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.

Sign up for GitHub

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

Jump to bottom

Packetbeat - Cannot monitor ICMP by itself #757

Closed

andrewkroh opened this issue Jan 18, 2016 · 0 comments

Labels

Member

andrewkroh 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

The text was updated successfully, but these errors were encountered:

andrewkroh added bug Packetbeat labels

andrewkroh mentioned this issue

Create a proper ICMP only BPF filter #759

Merged

ruflin closed this as completed in #759

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