* [Bloat] transparenty bridge/tap with fq_codel
@ 2019-03-11 23:01 Dev
2019-03-12 1:04 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Dev @ 2019-03-11 23:01 UTC (permalink / raw)
To: bloat
I built a transparent bridge on a Debian platform earlier running fq_codel between eth2 and eth3 as br0 which seemed to improve throughput.
Now, I’m wondering if there’s a way to copy some of those packets to another onboard NIC eth4 for analysis on another box on the network. How significant of a performance hit will this be on commodity hardware on my bridge throughput, and/or what is best practices? Has anyone already done this and made it work?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bloat] transparenty bridge/tap with fq_codel
2019-03-11 23:01 [Bloat] transparenty bridge/tap with fq_codel Dev
@ 2019-03-12 1:04 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2019-03-12 1:04 UTC (permalink / raw)
To: Dev; +Cc: bloat
On Mon, 11 Mar 2019 16:01:36 -0700
Dev <dev@logicalwebhost.com> wrote:
> I built a transparent bridge on a Debian platform earlier running fq_codel between eth2 and eth3 as br0 which seemed to improve throughput.
>
> Now, I’m wondering if there’s a way to copy some of those packets to another onboard NIC eth4 for analysis on another box on the network. How significant of a performance hit will this be on commodity hardware on my bridge throughput, and/or what is best practices? Has anyone already done this and made it work?
It is possible to do this with ingress qdisc and a mirred filter to mirror packets to another device. That is the Linux way to create SPAN ports on a bridge.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-03-12 1:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-11 23:01 [Bloat] transparenty bridge/tap with fq_codel Dev
2019-03-12 1:04 ` Stephen Hemminger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox