Date: Tue, 23 Jul 2013 10:17:01 -0400 From: Zaphod Beeblebrox <zbeeble@gmail.com> To: Kimmo Paasiala <kpaasial@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org>, Kevin Day <kevin@your.org> Subject: Re: Duplicate Address Detection misfire? Message-ID: <CACpH0Mc2-QaZhVCgHjLF0rj=VERjVB_q835dLYzwFXhd6RUAYA@mail.gmail.com> In-Reply-To: <CA%2B7WWSemtD_JCp8GBwAFRYay%2B83CjgQeqi2w6OR_JauNZrvs0Q@mail.gmail.com> References: <CACpH0McSM7HDeJcQ1pLcXuEZ96n=15YmCaP4YheZghBbyEgfUw@mail.gmail.com> <06BA4BD5-BE4E-4184-AFBB-D7FD4B2597D9@your.org> <CACpH0MdBk6aQhO6CugaiKTTv0GOS6dNeegwnxFSsd4n0mUOSmA@mail.gmail.com> <CACpH0MeemqKt4MEDw4PjycgA4PE4ejihJu9_G=Y9C2kZLdzXPA@mail.gmail.com> <CACpH0MdzB7hurx0Dk7Z09bMrXRmR8X%2BregphVgS0L7nGS%2B22XQ@mail.gmail.com> <CA%2B7WWSemtD_JCp8GBwAFRYay%2B83CjgQeqi2w6OR_JauNZrvs0Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Does that mean, then, that the only fix open to some people is to turn off DAD? I have another idea: Require DAD to inspect the sending MAC address. If the sending MAC address is _our_ MAC address, then the packet is not an indication of a duplicate address? On Tue, Jul 23, 2013 at 2:15 AM, Kimmo Paasiala <kpaasial@gmail.com> wrote: > On Tue, Jul 23, 2013 at 8:44 AM, Zaphod Beeblebrox <zbeeble@gmail.com> > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0Mc2-QaZhVCgHjLF0rj=VERjVB_q835dLYzwFXhd6RUAYA>