NAME<\/a> tunnel_key – Tunnel metadata manipulation<\/p>\n tc<\/b> … action tunnel_key<\/b> { unset<\/b> | SET<\/i> }<\/p>\n SET<\/i> := set src_ip<\/b> ADDRESS<\/i> dst_ip<\/b> ADDRESS<\/i> id<\/b> KEY_ID<\/i> dst_port<\/b> UDP_PORT<\/i> tos<\/b> TOS<\/i> ttl<\/b> TTL<\/i> [ csum<\/b> | nocsum<\/b> ]<\/p>\n The tunnel_key<\/b> action combined with a shared IP tunnel device, allows to perform IP tunnel en- or decapsulation on a packet, reflected by the operation modes UNSET<\/i> and SET<\/i>. The UNSET<\/i> mode is optional – even without using it, the metadata information will be released automatically when packet processing will be finished. UNSET<\/i> function could be used in cases when traffic is forwarded between two tunnels, where the metadata from the first tunnel will be used for encapsulation done by the second tunnel. SET<\/i> mode requires the source and destination ip ADDRESS<\/i> and the tunnel key id KEY_ID<\/i> which will be used by the ip tunnel shared device to create the tunnel header. The tunnel_key<\/b> action is useful only in combination with a mirred redirect<\/b> action to a shared IP tunnel device which will use the metadata (for SET<\/i> ) and unset the metadata created by it (for UNSET<\/i> ).<\/p>\n unset<\/b><\/p>\n<\/td>\n Unset the tunnel metadata created by the IP tunnel device. This function is not mandatory and might be used only in some specific use cases (as explained above).<\/p>\n<\/td>\n<\/tr>\n set<\/b><\/p>\n<\/td>\n Set tunnel metadata to be used by the IP tunnel device. Requires src_ip<\/b> and dst_ip<\/b> options. id<\/b> , dst_port<\/b> , geneve_opts<\/b> , vxlan_opts<\/b> and erspan_opts<\/b> are optional.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n id<\/b><\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n