netdev - Re: [RFC Patch net-next] vxlan: add ipv6 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Feb 2013 10:33:11 +0000
From:	Thomas Graf <tgraf@...g.ch>
To:	Cong Wang <amwang@...hat.com>
Cc:	netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...tta.com>
Subject: Re: [RFC Patch net-next] vxlan: add ipv6 support

On 02/28/13 at 02:01pm, Cong Wang wrote:
> WARNING: This is just an RFC patch, it only compiles!!
> 
> This patch adds IPv6 support to vxlan device, as the new version
> RFC already mentioned it:
> 
> 	http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-03
> 
> I am not sure if the following trick will work:
> 
> 	+       if (nla_len(nla) == sizeof(__be32)) {
> 	+               ip->ip4 = nla_get_be32(nla);
> 	+               ip->proto = htons(ETH_P_IP);
> 	+       }
> 	+#if IS_ENABLED(CONFIG_IPV6)
> 	+       else if (nla_len(nla) == sizeof(struct in6_addr)) {
> 	+               nla_memcpy(&ip->ip6, nla, sizeof(struct in6_addr));
> 	+               ip->proto = htons(ETH_P_IPV6);
> 	+       }
> 	+#endif
> 
> otherwise we have to introduce some new netlink attributes for
> IPv6 addresses? Any comments?

How about setting ndm_family to AF_INET6 and parse NDA_DST based on
that?

Assuming that nla_len(NDA_DST) > 4 == ip6 is a bit weak as like with
any Netlink attribute we only ever enforce a minimum length and never
a maximum or exact length.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html