On Thu, 4 Oct 2018 02:03:42 +0200, Pablo Neira Ayuso wrote: > Hi, > > The following patchset adds a new field to the tunnel metadata template > to restrict the configuration to a given tunnel driver. Currently, a > misconfiguration may result in packets going to the wrong tunnel driver. > > Although we have the tunnel option flags, they are not mandatory for > some tunnel drivers, eg. vxlan, which may use it or not; and gre which > does not use them. Option flags are necessary because interpretation of option blob is entirely protocol-specific. > This patch updates tc's tunnel action and netfilter's tunnel extension > to use this new field. OVS netlink interface has been left unset, although they > could be updated to use this. > > By extending the existing tc action to support the IP_TUNNEL_INFO_BRIDGE > mode, I think it should be possible to expose IP_TUNNEL_TYPE_VLAN too, > although this patchset doesn't address this scenario. > > The field is initialized to zero, which maps to IP_TUNNEL_TYPE_UNSPEC to > retain the existing behaviour, so the existing flexibility is still in > place while this new feature is added. > > Cc'ing people that git annotate show as dealing with these bits more > recently. What practical scenario are you trying to address here? Have you seen https://www.mail-archive.com/netdev@xxxxxxxxxxxxxxx/msg250705.html ?
