From: Andrew Lunn <andrew@lunn.ch>
To: Craig McGeachie <slapdau@gmail.com>
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: Sun, 19 Aug 2018 03:32:44 +0200 [thread overview]
Message-ID: <20180819013244.GA8950@lunn.ch> (raw)
In-Reply-To: <20180819010739.26975-1-slapdau@gmail.com>
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 up with DDP and sets the Appletalk node
> address, the kernel AARP code sends a probe packet for the address. It
> then receives its own probe packet and interprets that as some other
> node also trying to claim the address. It increments the address, tries
> again, and fails again ad nausium. Eventually the kernel module gives up
> and returns to netatalk which terminates with an error that it cannot
> get a node address.
Hi Craig
What Ethernet device are you seeing this problem with?
I'm not sure an Ethernet device should receive its own broadcasts.
This might be a driver bug, not an AARP bug.
Andrew
next prev parent reply other threads:[~2018-08-19 4:42 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 ` Andrew Lunn [this message]
2018-08-19 2:09 ` [RFC 0/1] Appletalk AARP probe broken by receipt of own broadcasts 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
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=20180819013244.GA8950@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=slapdau@gmail.com \
--cc=slapdau@yahoo.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.