On 08/28/15 at 08:48pm, Jiri Benc wrote: > By default (subject to the sysctl settings), IPv6 sockets listen also for > IPv4 traffic. Vxlan is not prepared for that and expects IPv6 header in > packets received through an IPv6 socket. > > In addition, it's currently not possible to have both IPv4 and IPv6 vxlan > tunnel on the same port (unless bindv6only sysctl is enabled), as it's not > possible to create and bind both IPv4 and IPv6 vxlan interfaces and there's > no way to specify both IPv4 and IPv6 remote/group IP addresses. > > Set IPV6_V6ONLY on vxlan sockets to fix both of these issues. This is not > done globally in udp_tunnel, as l2tp and tipc seems to work okay when > receiving IPv4 packets on IPv6 socket and people may rely on this behavior. > The other tunnels (geneve and fou) do not support IPv6. > > Signed-off-by: Jiri Benc <[email protected]>
Can we fix VXLAN instead? It should be possible to receive and send both v4 and v6 frames and represent it with metadata on a single socket. Maybe set the flag if IFLA_VXLAN_COLLECT_METADATA is not set? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
