From: Roman Mashak <mrv@mojatatu•com>
To: Or Gerlitz <ogerlitz@mellanox•com>
Cc: David Ahern <dsahern@gmail•com>, netdev@vger•kernel.org
Subject: Re: [PATCH iproute2/next 1/2] tc/act_tunnel_key: Enable setup of tos and ttl
Date: Thu, 19 Jul 2018 07:48:44 -0400 [thread overview]
Message-ID: <85fu0fbg4j.fsf@mojatatu.com> (raw)
In-Reply-To: <1531998135-13395-2-git-send-email-ogerlitz@mellanox.com> (Or Gerlitz's message of "Thu, 19 Jul 2018 14:02:14 +0300")
Or Gerlitz <ogerlitz@mellanox•com> writes:
> Allow to set tos and ttl for the tunnel.
>
> For example, here's encap rule that sets tos to the tunnel:
>
> tc filter add dev eth0_0 protocol ip parent ffff: prio 10 flower \
> src_mac e4:11:22:33:44:50 dst_mac e4:11:22:33:44:70 \
> action tunnel_key set src_ip 192.168.10.1 dst_ip 192.168.10.2 id 100 dst_port 4789 tos 0x30 \
> action mirred egress redirect dev vxlan_sys_4789
>
> Signed-off-by: Or Gerlitz <ogerlitz@mellanox•com>
> Reviewed-by: Roi Dayan <roid@mellanox•com>
> Acked-by: Jiri Pirko <jiri@mellanox•com>
[...]
Or, could you also update tunnel_key actions for the new options in
$(kernel)/tools/testing/selftests/tc-testing/tc-tests/actions/tunnel_key.json
once the patches are accepted ?
next prev parent reply other threads:[~2018-07-19 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 11:02 [PATCH iproute2/next 0/2] set/match the tos/ttl fields of TC based IP tunnels Or Gerlitz
2018-07-19 11:02 ` [PATCH iproute2/next 1/2] tc/act_tunnel_key: Enable setup of tos and ttl Or Gerlitz
2018-07-19 11:48 ` Roman Mashak [this message]
2018-07-19 17:14 ` Or Gerlitz
2018-07-19 11:02 ` [PATCH iproute2/next2/next 2/2] tc/flower: Add match on encapsulating tos/ttl Or Gerlitz
2018-07-20 16:01 ` [PATCH iproute2/next 0/2] set/match the tos/ttl fields of TC based IP tunnels David Ahern
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=85fu0fbg4j.fsf@mojatatu.com \
--to=mrv@mojatatu$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ogerlitz@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox