From: Stephen Hemminger <shemminger@vyatta.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [RFC PATCH 1/4] net: port mirroring: add tracepoints to appropriate network paths
Date: Tue, 15 Dec 2009 09:54:06 -0800 [thread overview]
Message-ID: <20091215095406.135fadbb@s6510> (raw)
In-Reply-To: <20091215174956.GC20644@hmsreliant.think-freely.org>
On Tue, 15 Dec 2009 12:49:56 -0500
Neil Horman <nhorman@tuxdriver.com> wrote:
> On Tue, Dec 15, 2009 at 09:22:22AM -0800, Stephen Hemminger wrote:
> > On Tue, 15 Dec 2009 12:02:49 -0500
> > Neil Horman <nhorman@tuxdriver.com> wrote:
> >
> > > On Tue, Dec 15, 2009 at 08:44:24AM -0800, Stephen Hemminger wrote:
> > > > On Tue, 15 Dec 2009 11:36:04 -0500
> > > > Neil Horman <nhorman@tuxdriver.com> wrote:
> > > >
> > > > > Add net_dev_xmit & net_dev_receive tracepoints
> > > > >
> > > > > Add tracepoints at the end of the network stack xmit path and the start of the
> > > > > stack receive path. Among other uses, these tracepoints can be used to tap the
> > > > > raw input and output streams for any given network device for the purposes of
> > > > > mirroring that traffic to other ports.
> > > > >
> > > >
> > > > There already is a mirroring solution but people don't know how to use it.
> > > > Using mirred on ingress qdisc does that.
> > > >
> > > I wish that had been easier to find. That only appears to mirror inbound frames
> > > though, what about outbound frames? can you attach mirred to an outbound qdisc?
> >
> > It works for outbound frames as well.
> *Sigh*, well there goes a weeks worth of tinkering. Stupid of me. Rescinded
> Thanks
> Neil
The tracepoints are still useful, and all is not wasted.
next prev parent reply other threads:[~2009-12-15 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 16:29 [RFC PATCH 0/4] net: Add port mirroring support to the kernel Neil Horman
2009-12-15 16:36 ` [RFC PATCH 1/4] net: port mirroring: add tracepoints to appropriate network paths Neil Horman
2009-12-15 16:44 ` Stephen Hemminger
2009-12-15 17:02 ` Neil Horman
2009-12-15 17:22 ` Stephen Hemminger
2009-12-15 17:49 ` Neil Horman
2009-12-15 17:54 ` Stephen Hemminger [this message]
2009-12-15 20:41 ` Neil Horman
2009-12-15 21:50 ` Stephen Hemminger
2009-12-16 12:00 ` Neil Horman
2009-12-15 16:37 ` [RFC PATCH 2/4] net: port mirroring: add port mirroring core code to kernel Neil Horman
2009-12-15 16:38 ` [RFC PATCH 3/4] net: port mirroring: add config options to enable port mirroring Neil Horman
2009-12-15 16:54 ` [RFC PATCH 4/4] net: port mirroring: Add maintainer Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091215095406.135fadbb@s6510 \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).