From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Amir Vadai <amir@vadai.me>, Jiri Pirko <jiri@resnulli.us>,
Cong Wang <xiyou.wangcong@gmail.com>,
John Fastabend <john.fastabend@gmail.com>,
Jiri Pirko <jiri@mellanox.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>,
Hadar Har-Zion <hadarh@mellanox.com>,
Oded Shanoon <odeds@mellanox.com>,
Amir Vadai <amirva@mellanox.com>
Subject: Re: [RFC net-next 0/2] net/sched: cls_flower, act_mirred: VXLAN redirect using TC
Date: Mon, 15 Aug 2016 13:24:36 +0300 [thread overview]
Message-ID: <20160815132436.0d1e34b6@pixies> (raw)
In-Reply-To: <faa0a9ab-fc02-543e-c60a-0d22b253a830@mojatatu.com>
On Mon, 15 Aug 2016 06:08:10 -0400, jhs@mojatatu.com wrote:
> On 16-08-15 05:08 AM, Amir Vadai wrote:
> > # 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 \
> > action mirred egress redirect dev $VXLAN
>
> Assuming $VXLAN is actually not a linux netdev of type vxlan?
> then the action does vxlan encap redirect sends it to the $VXLAN
> dev with encapsulation in place.
I assume Amir refers to vxlan netdev in VXLAN_F_COLLECT_METADATA mode,
using the tun_info metadata found in skb_metadata_dst.
The action is supposed to assign the tun metadata.
next prev parent reply other threads:[~2016-08-15 10:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 14:06 [RFC net-next 0/2] net/sched: cls_flower, act_mirred: VXLAN redirect using TC Amir Vadai
2016-08-14 14:06 ` [RFC net-next 1/2] net/sched: cls_flower: Introduce classify by vxlan outer headers Amir Vadai
2016-08-14 14:06 ` [RFC net-next 2/2] net/sched: act_mirred: Introduce vxlan support Amir Vadai
2016-08-14 17:53 ` [RFC net-next 0/2] net/sched: cls_flower, act_mirred: VXLAN redirect using TC Cong Wang
2016-08-15 5:05 ` John Fastabend
2016-08-15 7:11 ` Jiri Pirko
2016-08-15 8:17 ` Amir Vadai
2016-08-15 9:08 ` Amir Vadai
2016-08-15 9:48 ` Jiri Pirko
2016-08-15 9:50 ` Shmulik Ladkani
2016-08-15 9:58 ` Amir Vadai
2016-08-15 10:42 ` Shmulik Ladkani
2016-08-15 10:08 ` Jamal Hadi Salim
2016-08-15 10:24 ` Shmulik Ladkani [this message]
2016-08-15 10:41 ` Jamal Hadi Salim
2016-08-15 11:36 ` Amir Vadai
2016-08-15 16:35 ` John Fastabend
2016-08-15 12:34 ` Jiri Pirko
2016-08-15 12:59 ` Amir Vadai
2016-08-15 16:37 ` John Fastabend
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=20160815132436.0d1e34b6@pixies \
--to=shmulik.ladkani@gmail.com \
--cc=amir@vadai.me \
--cc=amirva@mellanox.com \
--cc=hadarh@mellanox.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=odeds@mellanox.com \
--cc=ogerlitz@mellanox.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.