From owner-freebsd-net@FreeBSD.ORG Tue Jul 23 06:15:12 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C52A9126 for ; Tue, 23 Jul 2013 06:15:12 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B5C82929 for ; Tue, 23 Jul 2013 06:15:12 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id bv4so1622446qab.13 for ; Mon, 22 Jul 2013 23:15:11 -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=JLORlYBqMRki0FIbpkqvTACjIv11gil5JS/QOP1osVc=; b=hOrUa6GnPwNmuu184po1RQms3+yxNlppV8qX2/aWUs+P0o5Unm+xRFLRSXKlfL/Q0/ +2Jpz6pthfZx+Sfrwh+dnhCYZAaOlBpvXjv3q7Rfjl1UGzJcYNP3+bEW+GSbMYUklGDP 0T+S5qEfVXHRycjAuFBOy1AXvG/0vWDBOYuBf4X5BW1IIMV2JrhLjJ9DPf0VK1vquCg2 YTx9L7C9pj2vaxGdqHs3L6EVS/WIbT/EsQ0yLbbo4Bu+a++Xdb5LBCm5EHAcKWTmYXUt KVRGhCUy+PYUs4QLlWGLU67+hdV5XtTohX/GFkVBqSVEERwjfK1u18xfMYzkGjr1Imj7 lLZw== MIME-Version: 1.0 X-Received: by 10.49.127.4 with SMTP id nc4mr36725444qeb.41.1374560111681; Mon, 22 Jul 2013 23:15:11 -0700 (PDT) Received: by 10.224.78.194 with HTTP; Mon, 22 Jul 2013 23:15:11 -0700 (PDT) In-Reply-To: References: <06BA4BD5-BE4E-4184-AFBB-D7FD4B2597D9@your.org> Date: Tue, 23 Jul 2013 09:15:11 +0300 Message-ID: Subject: Re: Duplicate Address Detection misfire? From: Kimmo Paasiala To: Zaphod Beeblebrox Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net , Kevin Day 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: Tue, 23 Jul 2013 06:15:12 -0000 On Tue, Jul 23, 2013 at 8:44 AM, Zaphod Beeblebrox wrote: > What to do when you don't trust the interface? VMWare is obviously > emulating the hardware and their interpretation of what the hardware "is" > is possibly different from ours. > > If I boot single-user and tcpdump the interface, I see two transmitted > solicitations. The kernel claims to have sent one. > > My concern: is the vmware interface reflecting the solicitation packet > because it is a broadcast packet? > > To determine this, I've gone over the tcpdump and pcap-filter man pages to > look for a way to only dump packets leaving from or arriving at an > interface. Can this be done? > > If VMWare is reflecting the packet back, I'm curious as to how we can fix > this. > > That sounds exactly like my experience with DAD misbehaving on my Zyxel WAP3205 access point. It is reflecting the multicasts (I hope that's the right term) so that any IPv6 equipment on the wireless network will think that its address is already in use. For the record, the client machines in my case are all OS X. Nice to know I'm not the only one with such problems. -Kimmo