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.
