Re: [pmacct-discussion] sfacct feature suggestion - traffic in/out direction

2016-07-28 Thread Paolo Lucente
Hi Jordan, Inline: On Thu, Jul 28, 2016 at 12:01:47AM +0300, Jordan wrote: > I mean that when you enable sflow on an interface you cannot > configure ingress/egress option. > It captures both directions while we need only data for ingress traffic. Just curious, which device is this? Never seen

Re: [pmacct-discussion] sfacct feature suggestion - traffic in/out direction

2016-07-27 Thread Jordan
Hello, I mean that when you enable sflow on an interface you cannot configure ingress/egress option. It captures both directions while we need only data for ingress traffic. There are two major problems with your solution. I think /direction /is not a valid sfacct key and we already use preta

Re: [pmacct-discussion] sfacct feature suggestion - traffic in/out direction

2016-07-27 Thread Jentsch, Mario
Hi Jordan, not sure what you mean with “equipment that cannot separate inbound/outbound traffic” but as long as you have direction in your flow data you can add a pre-tag map like ! ! tag=1 - inbound IPv4 traffic ! tag=2 - outbound IPv4 traffic ! tag=3 - inbound IPv6 traffic ! ta