From mboxrd@z Thu Jan 1 00:00:00 1970 From: Craig McGeachie Subject: Re: [RFC 0/1] Appletalk AARP probe broken by receipt of own broadcasts. Date: Tue, 21 Aug 2018 18:07:10 +1200 Message-ID: <7fc030aa-c648-4097-2205-0cbb7c7d095c@gmail.com> References: <20180819010739.26975-1-slapdau@gmail.com> <20180819013244.GA8950@lunn.ch> <20180819144107.GA23981@lunn.ch> <43f861ad-1e40-7e6e-b90c-ce410c60df94@gmail.com> <20180820132831.GA6583@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , netdev@vger.kernel.org, Craig McGeachie To: Andrew Lunn Return-path: Received: from mail-pf1-f177.google.com ([209.85.210.177]:41834 "EHLO mail-pf1-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726115AbeHUJ2H (ORCPT ); Tue, 21 Aug 2018 05:28:07 -0400 Received: by mail-pf1-f177.google.com with SMTP id y10-v6so7965478pfn.8 for ; Mon, 20 Aug 2018 23:09:25 -0700 (PDT) In-Reply-To: <20180820132831.GA6583@lunn.ch> Content-Language: en-NZ Sender: netdev-owner@vger.kernel.org List-ID: On 21/08/18 01:28, Andrew Lunn wrote: >> Turns out the problem is WinPCAP running on the host system (Windows >> 10). > It would be good to report this to the WinPCAP people. I hate it when > debug tools actually introduce bugs. This will take me some time. I couldn't fairly blame WinPCAP. Firstly, WinPCAP isn't really supported on Windows 10 (hence the fork, Win10PCAP). Secondly, right now all that I know is that it's some combination of WinPCAP and the virtual Intel 82540EM NIC. I'll have to play around a bit; maybe try some of the other virtual NICs. Then I think it would be good to have a more convenient test case than "First, install netatalk 2.2.6." I'll see if I can make one. Cheers, Craig.