[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160815125039.07809d54@pixies>
Date: Mon, 15 Aug 2016 12:50:39 +0300
From: Shmulik Ladkani <shmulik.ladkani@...il.com>
To: Amir Vadai <amir@...ai.me>
Cc: Jiri Pirko <jiri@...nulli.us>,
Cong Wang <xiyou.wangcong@...il.com>,
John Fastabend <john.fastabend@...il.com>,
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 Mon, 15 Aug 2016 12:08:04 +0300, amir@...ai.me wrote:
>
> Any objection to the following?
>
> # ENCAP rule
> tc filter add dev $ETH protocol ip parent ffff: prio 10 \
> flower ip_proto 1 \
> action set_tunnel_key src_ip 11.11.0.1 dst_ip 11.11.0.2 key_id 11 dst_port 4789 \
Ability to control few tun_flags (e.g. TUNNEL_CSUM, TUNNEL_DONT_FRAGMENT)
might be useful too.
> # DECAP rule
> tc filter add dev $VXLAN protocol ip parent ffff: prio 10 \
> flower \
> enc_src_ip 11.11.0.2 enc_dst_ip 11.11.0.1 enc_key_id 11 \
> ip_proto 1 \
You might want to match the tunnel's udp port as well, for symmetry.
Powered by blists - more mailing lists