On Mon, 13 Jan 2014, Paolo Lucente wrote:
libpcap is leveraged for filtering purposes ('filter'
keyword in pre_tag_map and 'aggregate_filter') and this is a known
limitation (perhaps the most annoying) of libpcap-based filters.
That makes sense. Thank you for your assistance.
--
Kind
On Fri, 10 Jan 2014, Paolo Lucente wrote:
To clarify: no traffic at all, both originated from and delivered
to your address blocks listed, gets tagged with 612/613/712/713.
Correct? Or some is and some is not?
Most is classified correctly, but about 7% doesn't match our filter.
tag
Hi Martin,
On Mon, Jan 13, 2014 at 02:45:25PM +0100, Martin Topholm wrote:
On Fri, 10 Jan 2014, Paolo Lucente wrote:
[ .. ]
Any chance the traffic is VLAN-tagged and/or MPLS-labelled and
VLAN tag and/or MPLS labels are exposed to pmacct via IPFIX? In
such a case you should reflect this
We're trying to use nfacctd version 1.5.0rc2 to classify groups of
traffic based on ip ranges within our network. We have Juniper routers
configured with inline jflow. During a consistentcy test we discovered
some traffic was missing.
In the example below we list all our networks in a filter. We
