[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85zhz4pjzs.fsf@mojatatu.com>
Date: Fri, 06 Jul 2018 09:32:55 -0400
From: Roman Mashak <mrv@...atatu.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: dsahern@...il.com, stephen@...workplumber.org,
oss-drivers@...ronome.com, netdev@...r.kernel.org,
Simon Horman <simon.horman@...ronome.com>,
Pieter Jansen van Vuuren
<pieter.jansenvanvuuren@...ronome.com>
Subject: Re: [PATCH iproute2-next] tc: m_tunnel_key: Add tunnel option support to act_tunnel_key
Jakub Kicinski <jakub.kicinski@...ronome.com> writes:
> From: Simon Horman <simon.horman@...ronome.com>
>
> Allow setting tunnel options using the act_tunnel_key action.
>
> Options are expressed as class:type:data and multiple options
> may be listed using a comma delimiter.
>
> # ip link add name geneve0 type geneve dstport 0 external
> # tc qdisc add dev eth0 ingress
> # tc filter add dev eth0 protocol ip parent ffff: \
> flower indev eth0 \
> ip_proto udp \
> action tunnel_key \
> set src_ip 10.0.99.192 \
> dst_ip 10.0.99.193 \
> dst_port 6081 \
> id 11 \
> geneve_opts 0102:80:00800022,0102:80:00800022 \
> action mirred egress redirect dev geneve0
[...]
Jakub, could you also add relevant tests for the new option in file
$(kernel)/tools/testing/selftests/tc-testing/tc-tests/actions/tunnel_key.json?
Powered by blists - more mailing lists