From: Craig McGeachie <slapdau@gmail•com>
To: Andrew Lunn <andrew@lunn•ch>
Cc: "David S. Miller" <davem@davemloft•net>,
netdev@vger•kernel.org, Craig McGeachie <slapdau@yahoo•com.au>
Subject: Re: [RFC 0/1] Appletalk AARP probe broken by receipt of own broadcasts.
Date: Tue, 21 Aug 2018 18:07:10 +1200 [thread overview]
Message-ID: <7fc030aa-c648-4097-2205-0cbb7c7d095c@gmail.com> (raw)
In-Reply-To: <20180820132831.GA6583@lunn.ch>
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.
prev parent reply other threads:[~2018-08-21 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 1:07 [RFC 0/1] Appletalk AARP probe broken by receipt of own broadcasts Craig McGeachie
2018-08-19 1:07 ` [RFC 1/1] appletalk: ignore aarp probe broadcasts that loopback Craig McGeachie
2018-08-19 1:32 ` [RFC 0/1] Appletalk AARP probe broken by receipt of own broadcasts Andrew Lunn
2018-08-19 2:09 ` Craig McGeachie
2018-08-19 14:41 ` Andrew Lunn
2018-08-20 8:48 ` Craig McGeachie
2018-08-20 13:28 ` Andrew Lunn
2018-08-21 6:07 ` Craig McGeachie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fc030aa-c648-4097-2205-0cbb7c7d095c@gmail.com \
--to=slapdau@gmail$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=slapdau@yahoo$(echo .)com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox