On Wed, Sep 13, 2017 at 12:25 PM, Simon Horman <simon.hor...@netronome.com> wrote: > On Tue, Sep 12, 2017 at 11:23:55PM +0300, Or Gerlitz wrote: >> On Tue, Sep 12, 2017 at 5:20 PM, Simon Horman >> <simon.hor...@netronome.com> wrote: >> > Allow matching on options in tunnel headers. >> > This makes use of existing tunnel metadata support. >> >> Simon, >> >> This patch is about matching on tunnel options, right? but >> >> > Options are a bytestring of up to 256 bytes. >> > Tunnel implementations may support less or more options, >> > or no options at all. >> > >> > # ip link add name geneve0 type geneve dstport 0 external >> > # tc qdisc add dev eth0 ingress >> > # tc qdisc del dev eth0 ingress; 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 4789 \ >> > id 11 \ >> > opts 0102800100800022 \ >> > action mirred egress redirect dev geneve0 >> >> the example here is on how to use tunnel options in the tunnel set key >> actions.. >> >> And the other way around in the other patch... the patch is about the >> tunnel key set action and the example shows how to match that in >> flower... I guess you want to swap the relevant of the change log. > > Yes, it seems so. Sorry about that.
no worries, you can do the swap, but before that >> Anyway, is there any human readable/understandable representation of >> these options? e.g what does 0102800100800022 means for geneve? > Thanks, I had not thought of that. My feeling is that could > be added to the tc tool as follow-up work. could you spend few words on the nature of these options now when we review the kernel patches? I guess this is somehow related to protocols such as geneve and vxlan-gpe -- it would be good if you elaborate on that a bit, does the kernel does any usage with these options beyond matching on them or stiching them to packet headers? Or.
