-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Warning about userland filtering always appears #134
Comments
Seen this also on all Linux based platforms, FreeBSD and OpenBSD does not report this. Might be that Linux actually does not support BPF on the interface that pcap opens, will look at it when I have time. |
FYI: I have just seen the same thing on our server, running CentOS 7. |
Does it mean capturing fails? |
No, not directly.
If filtering is not done at kernel level and your receiving a lot of
packets that are meant to be filtered it may have a huge impact on
processing when it's filtered higher up.
That may lead to drops that would not happen if it was done at kernel level.
|
Any idea when this will be fixed? I did not have this warning with the same bpf filter but with the older dsc collector (2012 ish) on CentOS 6 For the record, I am now getting this warning on a CentOS 7 with the latest dsc rpm collector Thanks |
The warning did not exist before, it is new and it can't be fixed in DSC
because it's a matter of what kernel API are available for libpcap.
It is just a warning, it's not fatal and if your filters are the same then
operational wise it is the same as before.
The warning does not appear on UNIX systems that have the right support for
kernel level filtering such as FreeBSD and OpenBSD.
The warning can also appear on these systems if the filter is too large to
fit within the kernel, then it's processed in userland.
|
Okay, thanks for this clear explanation |
I receive the
detected non-fatal error during pcap activation, filters may run in userland [11]: Resource temporarily unavailable
warning also when using short filters which do not cause any libcap warnings.The text was updated successfully, but these errors were encountered: