Netdev List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Dave Taht <dave.taht@gmail.com>, Mark Smith <markzzzsmith@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: "[RFC PATCH net-next 2/2] Reduce localhost to 127.0.0.0/16"
Date: Fri, 13 Sep 2019 11:01:59 -0600	[thread overview]
Message-ID: <9d2898f5-e5dc-a2ff-168d-22c69cca5f01@gmail.com> (raw)
In-Reply-To: <CAA93jw4SC2choBKXvaTD_5j93Op=RZ9ZEeKmyAu31ys_uNhSyA@mail.gmail.com>

On 9/13/19 10:14 AM, Dave Taht wrote:
> it came out that cumulus and a few others were possibly using high
> values of 127.x for switch chassis addressing, but we haven't got any
> documentation on how that works yet.

Not Cumulus.

I noted I am aware of 2 products from my history that use 127.x
addresses for communications within a box - e.g., to a bmc - that your
patch could break. Really it was meant as a data point that there are
released products that would be affected.

      reply	other threads:[~2019-09-13 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  8:54 "[RFC PATCH net-next 2/2] Reduce localhost to 127.0.0.0/16" Mark Smith
2019-09-13  9:14 ` Dave Taht
2019-09-13 17:01   ` David Ahern [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=9d2898f5-e5dc-a2ff-168d-22c69cca5f01@gmail.com \
    --to=dsahern@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=markzzzsmith@gmail.com \
    --cc=netdev@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