From: Lewis G Rosenthal <lgrosenthal@2rosenthals.com>
To: lartc@vger.kernel.org
Subject: Re: ARP flux vs. weak/strong ES model
Date: Fri, 15 Feb 2019 21:23:06 +0000 [thread overview]
Message-ID: <5C672DBA.5070507@2rosenthals.com> (raw)
Hi, Erik...
Erik Auerswald wrote:
> Hi,
>
> On 2/14/19 17:21, Grant Taylor wrote:
>> On 02/14/2019 01:31 AM, Erik Auerswald wrote:
<huge snip>
> Linux's cavalier default behaviour in answering ARP requests might be
> motivated by the weak ES model in helping other systems on the LAN
> reach the Linux server, even if they use an IP address assigned to
> another LAN the Linux server is connected to. Thus the problem of "ARP
> flux" is probably closely related to how Linux implements the weak ES
> model, but not necessarily to the weak ES model itself as described in
> RFC 1122.
>
> Thus I argue that using "ARP flux" to describe the ARP problem
> observed with Linux is preferable to attributing the problems to
> Linux's implementation of the weak ES model.
>
> Please note that I have not searched for the origin or an
> authoritative source on "ARP flux", and cannot guarantee that it is
> indeed consistently used to describe the aforementioned problem. But
> it did turn up on related web searches, and seems to directly refer to
> the ARP problem at hand.
>
> Sorry for being pedantic.
>
Thanks so much for a very cogent explanation of the difference. I'd been
meaning to do some digging since spying this thread scrolling by. One of
the things I like best about this list is the way it makes me scratch my
head. Usually, someone else comes up with a good answer before I'm done
scratching, which is another thing I like. :-)
Some interesting discussion of the Linux ARP flux problem, here (2.1.4
et seq):
http://linux-ip.net/html/ether-arp.html
Linked from there, and perhaps relevant to the original problem:
http://ja.ssi.bg/#iparp
(I guess I should probably push those to the original thread.)
--
Lewis
-------------------------------------------------------------
Lewis G Rosenthal, CNA, CLP, CLE, CWTS, EA
Rosenthal & Rosenthal, LLC www.2rosenthals.com
visit my IT blog www.2rosenthals.net/wordpress
-------------------------------------------------------------
next reply other threads:[~2019-02-15 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:23 Lewis G Rosenthal [this message]
2019-02-17 5:10 ` ARP flux vs. weak/strong ES model Grant Taylor
2019-02-18 0:37 ` Erik Auerswald
2019-02-18 2:18 ` Grant Taylor
2019-02-18 12:10 ` Erik Auerswald
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=5C672DBA.5070507@2rosenthals.com \
--to=lgrosenthal@2rosenthals.com \
--cc=lartc@vger.kernel.org \
/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.