From owner-freebsd-net@FreeBSD.ORG Fri Jul 19 01:21:13 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F1987AAD for ; Fri, 19 Jul 2013 01:21:12 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by mx1.freebsd.org (Postfix) with ESMTP id C03C25E0 for ; Fri, 19 Jul 2013 01:21:12 +0000 (UTC) Received: by mail-oa0-f41.google.com with SMTP id n10so5173714oag.14 for ; Thu, 18 Jul 2013 18:21:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mFgQ5LrlcV3BT3IcdqbITL2W/RE1n1TLrZID82HJJHY=; b=ZSOfg+JrHOLX+z09cXhPdT3KJZ7evzbdXv6whThrpullXSnM8AhHK6H58kREaoSVRp 5MOedhLyvmzEG8NL2eTaWnRkKXCF+L0a7RoSN6oSsLmm6kGLaRs9PfugPwlcOlVtZSmt 9Sbb1QOfw+R2lP0uBRZh84l3yqpEyEyzH9NwOiRnerG1AMQQOBy4VNFztnFNJyeIGmVL yse+77Ck6cMThe9Ipsj8KOY6viSMMbKImKeRmcI3vjDhd9bqW5Mqg8Z+yb57WKdwBeeZ VGKtAUZv07xCHxZth2FR5twhM05P51QV+aed1G/9F9VBL302bpZ2M0zJbuC5PbsbtyCV kbsQ== MIME-Version: 1.0 X-Received: by 10.60.102.202 with SMTP id fq10mr16144036oeb.42.1374196872293; Thu, 18 Jul 2013 18:21:12 -0700 (PDT) Received: by 10.76.13.35 with HTTP; Thu, 18 Jul 2013 18:21:12 -0700 (PDT) In-Reply-To: <06BA4BD5-BE4E-4184-AFBB-D7FD4B2597D9@your.org> References: <06BA4BD5-BE4E-4184-AFBB-D7FD4B2597D9@your.org> Date: Thu, 18 Jul 2013 21:21:12 -0400 Message-ID: Subject: Re: Duplicate Address Detection misfire? From: Zaphod Beeblebrox To: Kevin Day Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 01:21:13 -0000 On Sun, Jun 30, 2013 at 10:39 PM, Kevin Day wrote: > > On Jun 30, 2013, at 6:48 PM, Zaphod Beeblebrox wrote: > > > I have a FreeBSD 9.1-RELEASE vmware guest running. It is using the > > "bridged" type of networking with VMWare. It gets it's IPv4 address from > > DHCP (successfully) and then fails to initialize IPv6. The relevant > > rc.conf is: > > > > ipv6_activate_all_interfaces="YES" > > ifconfig_em0_ipv6="inet6 accept_rtadv" > > ip6addrctl_verbose="YES" > > > > The console output says: > > > > em0: DAD detected duplicate IPv6 address fe80:2::20c:29ff:fe0a:3989: NS > > in/out=2/1, NA in=0 > > em0: DAD complete for fe80:2::20c:29ff:fe0a:3989 - duplicate found > > em0: manual intervention required > > em0: possible hardware address duplication deteted, disable IPv6 > > > > And subsequently, em0's nd6 has "IFDISABLED" in it. > > > > With wireshark, I see two ICMPv6 neighbor solicitations that are > identical > > --- is this the problem? > > > > How do I fix this? > > Did you copy this VM and have both copies running at once? If so, it > assigned the same MAC address to each VM. > > VMware is suppose to detect this and ask if you "copied" or "moved" the > VM, and if you say "copied" it will randomly assign a new MAC to the VM. If > this didn't happen or if you said "moved" when you actually copied it, just > go in and delete/re-create the network interface in the VM's settings to > create a new MAC for it. > > If that's not the issue, we'd probably need more details about your > configuration. > To further diagnose, there is only one VM running. To ensure that there were no duplicates, I reassigned the MAC address in the VMWare configuration dialogue. Additionally, I tried stopping rtadvd on my router (no effect) and I tried putting the guest on a "host-only network" (basically isolated it) --- this clears the problem --- both the link-local and the static address are assigned. Frustrated, I dumped the windows interface that is bridged to the VMWare guest. When it boots, I see the following: 2461 19:24:16.376027000 Vmware_2e:46:fd Broadcast ARP 42 Gratuitous ARP for 66.96.20.42 (Request) 2462 19:24:16.388241000 :: ff02::1:ff00:42 ICMPv6 78 Neighbor Solicitation for 2001:1928:1::42 2463 19:24:16.389065000 :: ff02::1:ff00:42 ICMPv6 78 Neighbor Solicitation for 2001:1928:1::42 2464 19:24:16.444130000 :: ff02::16 ICMPv6 130 Multicast Listener Report Message v2 2465 19:24:16.444605000 :: ff02::16 ICMPv6 130 Multicast Listener Report Message v2 2466 19:24:16.594663000 :: ff02::1:ff2e:46fd ICMPv6 78 Neighbor Solicitation for fe80::250:56ff:fe2e:46fd 2467 19:24:16.595179000 :: ff02::1:ff2e:46fd ICMPv6 78 Neighbor Solicitation for fe80::250:56ff:fe2e:46fd 2753 19:24:22.274728000 Vmware_2e:46:fd Broadcast ARP 42 Who has 66.96.20.33? Tell 66.96.20.42 2754 19:24:22.274902000 Intel_bc:6f:87 Vmware_2e:46:fd ARP 60 66.96.20.33 is at 00:0e:0c:bc:6f:87 ... and then it goes on to chatter ipv4-wise as expected. Note that there are two of each packet. Is that normal? The ethernet source of all these packets is my vmware guest (save the who-has reply that I copied in).