3.25 Co-existing IPv4 and IPv6 VxLAN Workaround for UEK R4u2

Where VxLANs are configured for both IPv4 and IPv6 on the same host, there may be issues on UEK R4u2, due to the inability to bind the VxLAN tunnel on the same port and due to the way in which IPv6 sockets lists for IPv4 traffic as well. A patch has been applied in the RHCK, but the patch is not available in UEK R4u2.

To allow both versions of VxLAN to co-exist on the same system running Oracle Linux 7 update 3 when using UEK R4, enable the bindv6only system-wide socket option before bringing up the IPv6 VxLAN interface. You can disable the bindv6only system-wide socket option once the interface is online:

  1. Enable the bindv6only system-wide socket option:

    # sysctl -w net.ipv6.bindv6only=1
  2. Bring up the IPv6 interface, for example:

    # ip link set vlt2 up
  3. Disable the bindv6only system-wide socket option once you are certain that the IPv6 interface is up:

    # sysctl -w net.ipv6.bindv6only=0

(Bug ID 24579830)