From: Fan Du <fan.du@windriver.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: <netdev@vger.kernel.org>, <amwang@redhat.com>
Subject: Re: Kernel Panic in IPv6 vxlan
Date: Wed, 27 Nov 2013 16:25:30 +0800 [thread overview]
Message-ID: <5295AC7A.8020502@windriver.com> (raw)
In-Reply-To: <CAM3m09T2tuFCMjzdJq7AVBDnPeK0kVKt51JXsE954cHO6u_u2A@mail.gmail.com>
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
next prev parent reply other threads:[~2013-11-27 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 21:41 Kernel Panic in IPv6 vxlan Ryan Whelan
2013-11-27 8:25 ` Fan Du [this message]
2013-11-27 14:44 ` Ryan Whelan
2013-11-27 16:32 ` Stephen Hemminger
2013-11-27 8:46 ` [PATCH] {vxlan,inet6} Mark vxlan_dev flags with VXLAN_F_IPV6 Fan Du
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5295AC7A.8020502@windriver.com \
--to=fan.du@windriver.com \
--cc=amwang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rcwhelan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).