Re: [pmacct-discussion] nfacctd pretag.map with mpls_vpn_rd

2024-03-20 Thread Andrew Lake
map with MPLS labels but now in the software-defined world, potentially with controllers, that sporadically happens too. Paolo On 19/3/24 05:57, Andrew Lake wrote: > Hi Paolo, > > Ok maybe I have gotten headed down the wrong path. It sounds like you’re > saying nfacctd in normal

Re: [pmacct-discussion] nfacctd pretag.map with mpls_vpn_rd

2024-03-18 Thread Andrew Lake
the tee part barebone and implement these features in the collector? Just an idea as a perfectly valid answer could be that performing this enrichment in the replicator then also 3rd party tools could benefit from this info. Let me know. Paolo On 16/3/24 01:51, Andrew Lake wrote: > Hi Pa

Re: [pmacct-discussion] nfacctd pretag.map with mpls_vpn_rd

2024-03-15 Thread Andrew Lake
on GitHub? I'll flag it as Enhancement right away and will be able to make progress pretty soon for the VRF ID case. Paolo On 13/3/24 03:11, Andrew Lake wrote: > Hi, > > I recently tried creating a setup where I have an instance of nfacctd > running that has a pretag.map that I

[pmacct-discussion] nfacctd pretag.map with mpls_vpn_rd

2024-03-12 Thread Andrew Lake
Hi, I recently tried creating a setup where I have an instance of nfacctd running that has a pretag.map that I want to look at the value of mpls_vpn_rd as determined from the IPFIX record and then set a tag. The plan is to then use the tee plugin to send the IPFIX traffic to a different nfacctd