> The point here is that the filter doesn't contain any clause that matches
> host 10.0.0.39 ...
Because, I've changed 10.0.0.39 for 192.168.2.227 for the test.
Here the one in prod with 10.0.0.39:
[root@ntpprod ~]# /usr/bin/ntopng -i eth3 --packet-filter="ip and not proto
ipv6 and not ether
Gerard,
On Tue, Jan 10, 2017 at 10:13 PM, Gerhard Mourani
wrote:
> Simone,
>
> Here when launched from command line:
>
> [root@ntptest plugins]# /usr/bin/ntopng -i eth0 --packet-filter="ip and
> not proto ipv6 and not ether host ff:ff:ff:ff:ff:ff and not net (
> 224.0.0.0/8
Simone,
Here when launched from command line:
[root@ntptest plugins]# /usr/bin/ntopng -i eth0 --packet-filter="ip and not
proto ipv6 and not ether host ff:ff:ff:ff:ff:ff and not net (224.0.0.0/8 or
239.0.0.0/8) and not host (192.168.2.227)"
10/Jan/2017 16:10:46 [Ntop.cpp:1121] Setting local
Gerhard,
>From the logs I can't see anything that confirms ntopng has read/parsed the
bpf filter specified. It looks like the filter is ignored. I am not sure
those logs contain the full output, though.
Can you please run ntopng in foreground and paste the output? Simply call
Hi Tim,
can you please check the core affinity
[--core-affinity|-g] | Bind the capture/processing threads to
| specific CPU cores (specified as a comma-
| separated list)
and give every ntopng interface a different (better