netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: James Feeney <james@nurealm.net>
Cc: netdev@vger.kernel.org
Subject: Re: "local" interfaces, in forwarding state, are mutually "blind", and fail to connect
Date: Thu, 4 Jul 2019 19:46:05 +0200	[thread overview]
Message-ID: <20190704174605.GF13859@lunn.ch> (raw)
In-Reply-To: <a56eee49-49dc-1e61-19a4-6dfb6bd66f3e@nurealm.net>

On Thu, Jul 04, 2019 at 11:11:21AM -0600, James Feeney wrote:
> I have a question - maybe someone can point me in the right direction?
> 
> When there exist two or more "local" interfaces

Hi James

What exactly do you mean by a 'local' interface? The IP address on the
interface has scope local?

	  Andrew

      reply	other threads:[~2019-07-04 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 17:11 "local" interfaces, in forwarding state, are mutually "blind", and fail to connect James Feeney
2019-07-04 17:46 ` Andrew Lunn [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=20190704174605.GF13859@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=james@nurealm.net \
    --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;
as well as URLs for NNTP newsgroup(s).