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 for Android: free password hash cracker in your pocket

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

Message-ID: <5295AC7A.8020502@windriver.com>
Date:	Wed, 27 Nov 2013 16:25:30 +0800
From:	Fan Du <fan.du@...driver.com>
To:	Ryan Whelan <rcwhelan@...il.com>
CC:	<netdev@...r.kernel.org>, <amwang@...hat.com>
Subject: Re: Kernel Panic in IPv6 vxlan

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