Good Evening, I’m trying to configure pmacctd to aggregate inbound traffic by these primitives:
peer_src_as, src_as, src_std_comm The goal is to see if traffic from certain networks announced by carrier X with specific communities comes in from X or another hypothetical path (in that case the communities are not relevant, but that’s another story). My configuration is the following: machine running pmacctd sees the traffic thru 2 NICs, connected to SPAN port on core switches (where the carriers are linked); only inbound traffic is presented. I also setup a bgp peering with the border router, and enabled ADD-PATH capability on the session. The setup seems to work, the problem being that the community list always refers to the bgp best path; digging thru the documentation I see that in the ADD-PATH case, the method to select the relevant entry is looking at the bgp_next_hop of the flow…but I think that's actually applicable only to netflow/sflow collectors, right? I were wondering if it’s possible to extend bgp_peer_src_as_map to set the relevant information, so that every flow will have the community field populated by leveraging the same mechanics actually used to populate the peer_src_as field. Thank you Simone _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
