netdev - Re: Kernel Panic in IPv6 vxlan

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] [day] [month] [year] [list]

Date:	Wed, 27 Nov 2013 08:32:07 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Ryan Whelan <rcwhelan@...il.com>
Cc:	Fan Du <fan.du@...driver.com>, netdev@...r.kernel.org,
	amwang@...hat.com
Subject: Re: Kernel Panic in IPv6 vxlan

On Wed, 27 Nov 2013 09:44:03 -0500
Ryan Whelan <rcwhelan@...il.com> wrote:

> That isn't required with IPv4- if you don't specify an interface with
> IPv4, it looks like the system will route the multicast traffic via
> routing.  Is this not an option with IPv6?  I might be
> misunderstanding something?
> 
> thanks
> 
> On Wed, Nov 27, 2013 at 3:25 AM, Fan Du <fan.du@...driver.com> wrote:
> > Hallo,
> >
> >
> > On 2013年11月27日 05:41, Ryan Whelan wrote:
> >>
> >> I'm not sure if this is the right place to report this- please correct
> >> me if I'm mistaken.
> >>
> >> When creating a vxlan interface with an IPv6 multicast group but not
> >> specifying an underlying device, the kernel panics when the vxlan
> >> interface is brought up.  This doesn't happen with an IPv4 multicast
> >> group.  Linux 3.12.1 x86_64
> >>
> >> `ip link add vxlan0 type vxlan id 42 group ff0e::110`
> >
> >
> > You forgot to attach vxlan0 to a physical netdev ;) try:
> >
> > ip link add vxlan0 type vxlan id 42 group ff0e::110 dev ethX
> >
> > This will work anyway.
> >
> > --
> > 浮沉随浪只记今朝笑
> >
> > --fan fan
> --

Yes, this is a bug in the IPv6 implementation.
--
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