[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMiYRRgQiYdXoUVGh3gCtsqEmGH3+ZnMYt7+73oGzSrejg@mail.gmail.com>
Date: Thu, 19 Jul 2018 20:14:07 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Roman Mashak <mrv@...atatu.com>
Cc: Or Gerlitz <ogerlitz@...lanox.com>,
David Ahern <dsahern@...il.com>,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH iproute2/next 1/2] tc/act_tunnel_key: Enable setup of tos
and ttl
On Thu, Jul 19, 2018 at 2:48 PM, Roman Mashak <mrv@...atatu.com> wrote:
> Or Gerlitz <ogerlitz@...lanox.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@...lanox.com>
>> Reviewed-by: Roi Dayan <roid@...lanox.com>
>> Acked-by: Jiri Pirko <jiri@...lanox.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 ?
yes, I will do that
Powered by blists - more mailing lists