lartc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@tnetconsulting.net>
To: lartc@vger.kernel.org
Subject: Re: Using netem on one interface expands to all interfaces
Date: Thu, 14 Feb 2019 16:21:40 +0000	[thread overview]
Message-ID: <cb096bc8-8507-5376-598d-6dcea2196cb3@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <D5EA1F26-CCDC-49F0-A34E-33F3BBF5B094@proper.com>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

On 02/14/2019 01:31 AM, Erik Auerswald wrote:
> P.S. I am no longer sure if "strong host model" vs. "weak host model" 
> is the correct way to refer to this problem, as it concerns ARP, not IP 
> routing / interface selection. Nowadays it seems to be called "ARP flux."

I seem to run into "{strong,weak} {host,end system} model" references 
monthly in the various circles that I travel in.

I can't remember the last time I heard "ARP flux".

"{strong,weak} {host,end system} model" might refer to routing and not 
directly ARP, but it is decidedly adjacent and applicable.  All be it 
possibly not technically precise.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4008 bytes --]

      parent reply	other threads:[~2019-02-14 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 18:16 Using netem on one interface expands to all interfaces Paul Hoffman
2019-02-13 19:47 ` Grant Taylor
2019-02-13 22:35 ` Paul Hoffman
2019-02-13 22:52 ` Grant Taylor
2019-02-14  8:31 ` Erik Auerswald
2019-02-14 16:21 ` Grant Taylor [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=cb096bc8-8507-5376-598d-6dcea2196cb3@spamtrap.tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).