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
> Turns out the problem is WinPCAP running on the host system (Windows
> 10).
Hi Craig
It would be good to report this to the WinPCAP people. I hate it when
debug tools actually introduce bugs.
Andrew
On 20/08/18 02:41, Andrew Lunn wrote:
>> I run inside Virtualbox with the Realtek PCIe GBE Family Controller.
>>
>> Assuming I'm reading /sys/class/net/enp0s3/driver correctly, it's using the
>> e1000 driver.
>
> Hi Craig
Andrew,
My apologies. I've wasted your time. PEBKAC.
> Ah. And how do you
> I run inside Virtualbox with the Realtek PCIe GBE Family Controller.
>
> Assuming I'm reading /sys/class/net/enp0s3/driver correctly, it's using the
> e1000 driver.
Hi Craig
Ah. And how do you connect to the network? Please run some tcpdumps
and collect packets at various points. Make sure you
On 19/08/18 13:32, Andrew Lunn wrote:
On Sun, Aug 19, 2018 at 01:07:38PM +1200, Craig McGeachie wrote:
I'm hoping I can find someone able and willing to test this patch. That
requires someone still using netatalk 2.2.x with DDP, or some other DDP
userspace application. This feels like a longshot
On Sun, Aug 19, 2018 at 01:07:38PM +1200, Craig McGeachie wrote:
> I'm hoping I can find someone able and willing to test this patch. That
> requires someone still using netatalk 2.2.x with DDP, or some other DDP
> userspace application. This feels like a longshot.
>
> When netatalk 2.2.x starts u
I'm hoping I can find someone able and willing to test this patch. That
requires someone still using netatalk 2.2.x with DDP, or some other DDP
userspace application. This feels like a longshot.
When netatalk 2.2.x starts up with DDP and sets the Appletalk node
address, the kernel AARP code sends
