From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
nikolay@cumulusnetworks.com
Subject: Re: [PATCH v2 net-next 1/1] net sched actions: mirred add support for setting Dst MAC address
Date: Wed, 6 Jul 2016 06:02:51 -0400 [thread overview]
Message-ID: <577CD74B.5070805@mojatatu.com> (raw)
In-Reply-To: <CAM_iQpVrfmVW2m9u0tGfy=WA9joV7Ssu9V+DR+0kbm=yNQ8Yzw@mail.gmail.com>
On 16-07-05 02:19 PM, Cong Wang wrote:
> On Tue, Jul 5, 2016 at 4:04 AM, Jamal Hadi Salim <jhs@mojatatu.com> wrote:
>> Second arguement usability, from:
>> to:
>> $TC filter add dev $ETH parent 1: protocol ip prio 10 \
>> u32 match ip protocol 1 0xff flowid 1:2 \
>> action mirred egress redirect dev $SPANPORT dst 02:15:15:15:15:15
>>
>> given that I have to do this many many times in scripts and the
>> second policy is better eye candy.
>
> How about adding a "wrapper" in iproute2 pedit action to make
> it accept "dst mac xx:xx:xx:xx:xx:xx"? Like what we did for u32
> filters.
>
Thats what we do today. Its fugly and debugging is nasty
(having to stare at 10s or hundreds of outputs looking at
offset and bytes when something goes wrong).
It is ok to use pedit as a starting point because you can
quickly craft things without any kernel changes.
But when you start heavily using something handcrafted
its usability starts affecting you.
I will work on and send the skbmod patch next time i
get cycles.
cheers,
jamal
prev parent reply other threads:[~2016-07-06 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 14:34 [PATCH v2 net-next 1/1] net sched actions: mirred add support for setting Dst MAC address Jamal Hadi Salim
2016-07-02 15:16 ` Nikolay Aleksandrov
2016-07-02 16:58 ` Cong Wang
2016-07-02 21:38 ` Jamal Hadi Salim
2016-07-04 15:25 ` Jiri Pirko
2016-07-04 22:14 ` David Miller
2016-07-05 11:04 ` Jamal Hadi Salim
2016-07-05 18:19 ` Cong Wang
2016-07-06 10:02 ` Jamal Hadi Salim [this message]
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=577CD74B.5070805@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=xiyou.wangcong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.