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
scussion-boun...@pmacct.net]
*On Behalf Of *Jordan
*Sent:* Wednesday, July 27, 2016 5:06 PM
*To:* pmacct-discussion@pmacct.net
*Subject:* [pmacct-discussion] sfacct feature suggestion - traffic
in/out direction
Hello,
We're having issues with equipment that cannot separate
inbound/outb
and filter e.g. the ingress flows with
!
pre_tag_filter[ingress]: 1,3
aggregate[ingress]: …
!
Regards,
Mario
From: pmacct-discussion [mailto:pmacct-discussion-boun...@pmacct.net] On Behalf
Of Jordan
Sent: Wednesday, July 27, 2016 5:06 PM
To: pmacct-discussion@pmacct.net
Subject: [pmacct-discussion] sf
Hello,
We're having issues with equipment that cannot separate inbound/outbound
traffic using sflow V5.
Looking at the sflow V5 protocol it's having the following fields.
Usually they match the snmp interface indexes.
/source_id/
/interface input/
/interface output/
What I suggest as a new
