Running VXLANs over IPv6 link-local addresses allows to use them as a drop-in replacement for VLANs, avoiding to allocate additional outer IP addresses to run the VXLAN over.
Since v1, I have added a lot more consistency checks to the address configuration, making sure address families and scopes match. To simplify the implementation, I also did some general refactoring of the configuration handling in the new first patch of the series. The second patch is more cleanup; is slightly touches OVS code, so that list is in CC this time, too. As in v1, the last two patches actually make VXLAN over IPv6 link-local work, and allow multiple VXLANs wit the same VNI and port, as long as link-local addresses on different interfaces are used. As suggested, I now store in the flags field if the VXLAN uses link-local addresses or not. Matthias Schiffer (6): vxlan: refactor verification and application of configuration vxlan: get rid of redundant vxlan_dev.flags vxlan: improve validation of address family configuration vxlan: check valid combinations of address scopes vxlan: fix snooping for link-local IPv6 addresses vxlan: allow multiple VXLANs with same VNI for IPv6 link-local addresses drivers/net/vxlan.c | 411 ++++++++++++++++++++++++++---------------- include/net/vxlan.h | 3 +- net/openvswitch/vport-vxlan.c | 4 +- 3 files changed, 263 insertions(+), 155 deletions(-) -- 2.12.2