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]
Message-ID: <1366700341.21136.17.camel@cr0>
Date:	Tue, 23 Apr 2013 14:59:01 +0800
From:	Cong Wang <amwang@...hat.com>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [Patch net-next v5 0/5] vxlan: add ipv6 support

On Mon, 2013-04-22 at 23:51 -0700, Stephen Hemminger wrote:
> On Tue, 23 Apr 2013 14:27:35 +0800
> Cong Wang <amwang@...hat.com> wrote:
> 
> > After several tries, I think it is not easy to do at all, it relies on
> > some icmp functions at least, which are still compiled as a module. So,
> > I can't think out any easier solution than simply adding Kconfig
> > dependency.
> 
> Why is IPv6 support depending on ICMP functions? Everything doesn't
> have to be hyper optimized, at least not initially.

VXLAN relies on IPv6 multicast which is on top of ICMPv6. At very least
igmp6_send() calls icmpv6_flow_init() and icmp6_dst_alloc() in the code.

Bridge multicast snooping only parses some multicast packets, which
seems much easier than maintaining multicast group ownership.

Yeah, I definitely agree on that we can fix this later, if David has no
objections.

Thanks.

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ