From owner-freebsd-net@FreeBSD.ORG Wed Jul 24 00:53:29 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 9BCDE590 for ; Wed, 24 Jul 2013 00:53:29 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5D8392FA9 for ; Wed, 24 Jul 2013 00:53:29 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id jw11so6513658veb.4 for ; Tue, 23 Jul 2013 17:53:28 -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=txK2H165mbwo0R3vOb9ZESKZu4UeKN/SoSXbBBWMris=; b=umYjYN+Rvp88y7VM1+2yeNLwehle/viYsP8jr9bSAo44ARESVGQbxJfw6KJMkkghCV Fv43HOFCuoU0KIzGnjz62AzEGCflCpJ+sRUMXthg+6/gbOWvJPAGmmiW7gASL40Mn7HD vGkiLbqnp/odGiTRz4C+FoE4N0+hci9CSsuOo/WxmSC0W3x4fPg12M8v0LPn2gltk5x2 /OLb+MxhLfoYlaiQa5xm9RNWu67IU3tOLZZKbCxPLd/h7q0X1nH/53AA80p8wBAVlxR8 TD6CD+ntB4g6XY7Vxoz01VH3FwRqUgIp79kBQQ0A0dnkQq0a7s4/PoQyjAZttQn4CF5V V1YQ== MIME-Version: 1.0 X-Received: by 10.220.249.67 with SMTP id mj3mr4143559vcb.23.1374627208455; Tue, 23 Jul 2013 17:53:28 -0700 (PDT) Received: by 10.221.22.199 with HTTP; Tue, 23 Jul 2013 17:53:28 -0700 (PDT) In-Reply-To: <3341F665-B179-4A99-B48A-81EE3D0478A6@your.org> References: <06BA4BD5-BE4E-4184-AFBB-D7FD4B2597D9@your.org> <3341F665-B179-4A99-B48A-81EE3D0478A6@your.org> Date: Tue, 23 Jul 2013 20:53:28 -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: Wed, 24 Jul 2013 00:53:29 -0000 Ironically, the win 7 host is using an "em" series card. Specifically, an Intel "Gigabit CT". It is configured in vlan mode and the VMWare bridged connection is connected to a VLAN. Regardless, tho, Intel's own drivers are usually not this bad --- and the driver is up-to-date. On Tue, Jul 23, 2013 at 10:22 AM, Kevin Day wrote: > Sorry for the slow reply. > > We run mainly ESXi (the bare metal version of VMware, not the desktop > versions) but I do remember seeing something sort of similar on a desktop > version ages ago. Basically we narrowed it down to a Windows driver bug on > the host system's ethernet card. It was basically reflecting back > everything it transmitted into the receive queue. This was before IPv6 was > in use here, but I remember it breaking a file sharing protocol (SMB? AFP?) > that also didn't like seeing its own multicasts/broadcasts echoed back to > itself. > > By any chance is this on a system using WiFi rather than wired ethernet? > Many routers/access points/wifi adapters have problems with the idea of > VMware's "bridged mode" networking - they expect only one MAC per station > and do not do the right thing in some places. > > I don't have an answer for you, but I'd look at the physical networking > card/adapter on the host OS first if I were troubleshooting this. Updated > driver/replace with something else/etc. > > -- Kevin > > On Jul 23, 2013, at 12: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. > > > >