From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt 3.10.17-3 released
Date: Tue, 22 Oct 2013 16:45:41 -0700 [thread overview]
Message-ID: <20131022164541.7f6b09e5@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAA93jw7nDwteD7ELuVNY2MOvKrNtXWGeJ+_QjTpLR2iLYtWA-g@mail.gmail.com>
On Tue, 22 Oct 2013 16:27:02 -0700
Dave Taht <dave.taht@gmail.com> wrote:
> On Tue, Oct 22, 2013 at 4:12 PM, Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> > With TC you can apply an action to packets coming in.
> > One of those actions is mirred (not a typo) which mirrors the packet
> > to another device. There is both mirror and redirect possible.
> >
> > Jamal invented this years ago, but actions are not widely used.
>
> I use this technique for an input redirect into ifb for cerowrt's
> shaper. It works
> well.
>
> > Inside Vyatta CLI wrappers, the port-mirroring capability converts to tc
> > commands. For example doing SPAN equivalent from eth0 to eth1 is:
> >
> > tc filter add dev eth0 parent ffff: \
> > protocol all prio 10 u32 \
> > match u32 0 0 flowid 1:1 \
> > action mirred egress mirror dev eth1
>
> In this case the device on eth1 would have to be an entirely passive
> device otherwise it will attempt to interact with that traffic (?) In
> the case of cero, it has two ethernet devices available, one hooked
> directly into a switch, and as many wifi ones as you want. What would
> probably work would be to split off a dedicated vlan port for the
> mirror and send stuff to dev eth1.4 - (for example) so long as the
> listening server was entirely passive.
Yes, eth1 was assumed passive.
>
> tc filter add dev sw00 parent ffff: \
> protocol all prio 10 u32 \
> match u32 0 0 flowid 1:1 \
> action mirred egress mirror dev se00.4
That should work but doing mirror from se00 to se00.4 would create
a death spiral.
>
> but you'd also want to do it on ingress too. (?)
>
> I forget the syntax for splitting off a vlan port in cero...
>
> > The actions apply to a filter, and this seemed to be a workable (match all)
> > filter.
>
> Both directions?
This was done on ingress only.
next prev parent reply other threads:[~2013-10-22 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 20:45 Dave Taht
2013-10-21 21:04 ` Dave Taht
2013-10-22 1:34 ` Stephen Hemminger
2013-10-22 2:10 ` Dave Taht
2013-10-22 23:12 ` Stephen Hemminger
2013-10-22 23:27 ` Dave Taht
2013-10-22 23:45 ` Stephen Hemminger [this message]
2013-10-22 1:27 ` Richard E. Brown
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131022164541.7f6b09e5@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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