do agree with you that that would be intriguing (in general but perhaps
specifically) for all people that do rely on 3rd party services to run
their own infrastructure, thinking to L2/L3 MPLS VPNs and suchs.
Paolo
On 09/10/2020 13:28, Felix Stolba wrote:
> Hi ev
Hi everyone,
so recently the config parameter nfacctd_dtls_port was introduced. By using
this, pmacct can consume flow data contained in a DTLS stream as specified in
RFC5153.
Having an integrated, secure transport for flow data is an intriguing idea. But
that poses the question, how can such
Hey Steve
I'm assuming you're generating Netflow from locally received/generated traffic,
e.g. using pmacct as a Netflow probe. Therefore I think the option called
nfprobe_source_ip might be the one you're looking for.
Let me know if that fits your use-case.
Regards
Felix
Am 17.10.19,
Hi Moftah
In the docs [1] it’s stated that for networks_mask to work you have to include
the mask as an aggregation primitive. The config you posted earlier doesn't
seem to have that.
It should probably read something like that
aggregate[out6]: src_net, src_mask
Regards
Felix
[1]
Hey Brooks,
I can confirm I have a similar setup collecting Netflow so in principle this
should do what you want. The bgp_agent_map also looks fine, assuming birds
Router ID is 1.1.1.1?
Just a thought, as per the docs it’s recommended to set pmacctd_net to the same
value as pmacctd_as (bgp in
Hi
I’m trying to use a pre_tag_map with less than 5000 entries with the purpose of
adding the ingress and egress interface names to the flow records as labels.
When using this map, nfacctd reproducibly crashes, tested using 1.7.1 and
1.7.3. I would appreciate if someone (Paolo? :) ) could
