-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Zeek config with eth0 does not work #20
Comments
How did your config get eth0 in it if that's not an available interface? Did you configure the package using the graphical UI? It should show you a list of interfaces and you select from them. I searched the code base and the phrase 'eth0' appears three times in one file, and all of them are part of comments, i.e. not actually code that affects anything, so I'm not sure how this happened. |
Yes I used the graphical UI, selected WAN (em0) from the list of interfaces. |
We will dig deeper about it. |
Same problem for me, but one small observation. Thanks, |
Ah, sorry, forgot about tech details. I use pfSense 2.5.0 fresh installed. |
I have an upgrade crash report (to latest pfsense). Relevant part:
is this helpful ? |
Related to #22 |
The system has em0 instead of eth0:
==== stderr.log
fatal error: problem with interface eth0 (pcap_error: BIOCSETIF failed: Device not configured (pcap_activate))
==== stdout.log
max memory size (kbytes, -m) unlimited
data seg size (kbytes, -d) 33554432
virtual memory (kbytes, -v) unlimited
core file size (blocks, -c) unlimited
==== .cmdline
-i eth0 -U .status -p zeekctl -p zeekctl-live -p standalone -p local -p zeek local.zeek zeekctl zeekctl/standalone zeekctl/auto
The text was updated successfully, but these errors were encountered: