[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F92CE10540@HASMSX110.ger.corp.intel.com>
Date: Sun, 4 Sep 2016 18:19:24 +0000
From: "Rosen, Rami" <rami.rosen@...el.com>
To: Hadar Hen Zion <hadarh@...lanox.com>,
"David S. Miller" <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>, Jiri Benc <jbenc@...hat.com>,
Jamal Hadi Salim <jhs@...atatu.com>,
Shmulik Ladkani <shmulik.ladkani@...il.com>,
Tom Herbert <tom@...bertland.com>,
Eric Dumazet <edumazet@...gle.com>,
Cong Wang <xiyou.wangcong@...il.com>,
Amir Vadai <amirva@...lanox.com>,
Or Gerlitz <ogerlitz@...lanox.com>, Amir Vadai <amir@...ai.me>
Subject: RE: [PATCH net-next V5 4/4] net/sched: Introduce act_tunnel_key
Hi, Hadar,
>For example, the following flower filter will forward all ICMP packets destined to 11.11.11.2 >through the shared vxlan device 'vxlan0'. Before redirecting, a metadata for the vxlan tunnel >is created using the tunnel_key action and it's arguments:
Shouldn't it be "tc filter add dev ..."?
>$ filter add dev net0 protocol ip parent ffff: \
> flower \
> ip_proto 1 \
> dst_ip 11.11.11.2 \
> action tunnel_key set \
> src_ip 11.11.0.1 \
> dst_ip 11.11.0.2 \
> id 11 \
> action mirred egress redirect dev vxlan0
Regards,
Rami Rosen
Intel Corporation
Powered by blists - more mailing lists