[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpXetPgj_nCdYL73r_2hDRmnCpa0-WrxN-UbwBsdFgouiQ@mail.gmail.com>
Date: Sun, 14 Aug 2016 10:53:30 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Amir Vadai <amir@...ai.me>
Cc: Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...lanox.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Hadar Har-Zion <hadarh@...lanox.com>,
Oded Shanoon <odeds@...lanox.com>,
Amir Vadai <amirva@...lanox.com>
Subject: Re: [RFC net-next 0/2] net/sched: cls_flower, act_mirred: VXLAN
redirect using TC
On Sun, Aug 14, 2016 at 7:06 AM, Amir Vadai <amir@...ai.me> wrote:
> tc qdisc add dev $ETH ingress
>
> # ENCAP rule for ARP
> tc filter add dev $ETH protocol 0x806 parent ffff: prio 11 \
> flower \
> action mirred egress redirect dev $VXLAN enc_src_ip 11.11.0.1 enc_dst_ip 11.11.0.2 enc_key_id 11 enc_dst_port 4789
>
> # ENCAP rule for ICMP
> tc filter add dev $ETH protocol ip parent ffff: prio 10 \
> flower ip_proto 1 \
> action mirred egress redirect dev $VXLAN enc_src_ip 11.11.0.1 enc_dst_ip 11.11.0.2 enc_key_id 11 enc_dst_port 4789
>
I don't like this. This makes mirred action unnecessarily
complex, it should really just mirror or redirect packets as
it is, why it should be aware of tunnel information?
I think you probably need to introduce a new tc action
for these tunnel information and pipe it to mirred.
Powered by blists - more mailing lists