From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Kernel Panic in IPv6 vxlan Date: Wed, 27 Nov 2013 08:32:07 -0800 Message-ID: <20131127083207.7f97c3a4@nehalam.linuxnetplumber.net> References: <5295AC7A.8020502@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Fan Du , netdev@vger.kernel.org, amwang@redhat.com To: Ryan Whelan Return-path: Received: from mail-pd0-f181.google.com ([209.85.192.181]:36342 "EHLO mail-pd0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753338Ab3K0QcL (ORCPT ); Wed, 27 Nov 2013 11:32:11 -0500 Received: by mail-pd0-f181.google.com with SMTP id p10so10158919pdj.40 for ; Wed, 27 Nov 2013 08:32:11 -0800 (PST) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 27 Nov 2013 09:44:03 -0500 Ryan Whelan 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? >=20 > thanks >=20 > On Wed, Nov 27, 2013 at 3:25 AM, Fan Du wrote: > > Hallo, > > > > > > On 2013=C4=EA11=D4=C227=C8=D5 05:41, Ryan Whelan wrote: > >> > >> I'm not sure if this is the right place to report this- please cor= rect > >> me if I'm mistaken. > >> > >> When creating a vxlan interface with an IPv6 multicast group but n= ot > >> specifying an underlying device, the kernel panics when the vxlan > >> interface is brought up. This doesn't happen with an IPv4 multica= st > >> 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. > > > > -- > > =B8=A1=B3=C1=CB=E6=C0=CB=D6=BB=BC=C7=BD=F1=B3=AF=D0=A6 > > > > --fan fan > -- Yes, this is a bug in the IPv6 implementation.