Re: [pmacct-discussion] pmacctd and src_std_comm aggregation

2020-05-26 Thread Paolo Lucente
Ciao Simone, You see, that is the thing with the example you proposed: it is very likely that one of the two paths is not in the RIB (like you said) so you can't really make 'suggestions', you have to force it through a static mapping; i do see people being fine with that for the Peer Source ASN

Re: [pmacct-discussion] pmacctd and src_std_comm aggregation

2020-05-25 Thread Simone Ricci
Ciao Paolo, > Il giorno 25 mag 2020, alle ore 16:03, Paolo Lucente ha > scritto: > > Ciao Simone, > > If i got it correct you are after static mapping of communities to input > traffic - given an input interface / vlan or an ingress router or a > source MAC address. Yes, just to be clear imag

Re: [pmacct-discussion] pmacctd and src_std_comm aggregation

2020-05-25 Thread Paolo Lucente
Ciao Simone, If i got it correct you are after static mapping of communities to input traffic - given an input interface / vlan or an ingress router or a source MAC address. It seems doable, like you said, adding a machinery like it exists for the source peer ASN. I'd have one question for you:

[pmacct-discussion] pmacctd and src_std_comm aggregation

2020-05-24 Thread Simone Ricci
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