mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Derek Fawcus <dfawcus@cisco.com>
To: Yuji Sekiya <sekiya@sfc.wide.ad.jp>
Cc: "David S. Miller" <davem@redhat.com>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses
Date: Thu, 10 Oct 2002 02:11:54 +0100	[thread overview]
Message-ID: <20021010021154.G8102@edi-view1.cisco.com> (raw)
In-Reply-To: <un0pn9knb.wl@sfc.wide.ad.jp>; from sekiya@sfc.wide.ad.jp on Thu, Oct 10, 2002 at 09:56:24AM +0900

On Thu, Oct 10, 2002 at 09:56:24AM +0900, Yuji Sekiya wrote:
> 
> I can underdtand there is no interoperability issue with cisco box
> (with /10 link-local prefix ?) and USAGI kernel(with /64 link-local
> prefix). :-)

Mind it's interesting that the above currently works.  I suspect that
this is because the ping was originated on the cisco box,  and hence
ND was triggered,  with the linux box probably gleaning info from the
NS to create a STALE entry.  That STALE entry would then probably have
been probed to get a REACHABLE entry.

What happens if you clear the ND entries (on both boxes),  swap the
link local addresses,  then ping from the Linux box to the cisco box?

I suspect that the ping will fail.  As ND will never be triggered,  and
hence the host routes will not be created.

Another alternative would be if one was say fe80:1910::10 and the other
say fe80:2010::20,  that would probably fail with the ping originated
from the linux end,  but I'm not sure if the linux box would respond
when the ping was originated from the cisco end.  Assuming my guess
about the gleaning above is correct,  it probably will.

DF

  reply	other threads:[~2002-10-10  1:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 15:05 YOSHIFUJI Hideaki / 吉藤英明
2002-10-07 18:55 ` David S. Miller
2002-10-08  0:37   ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-08 19:40     ` David S. Miller
2002-10-09 16:00 ` Derek Fawcus
2002-10-09 16:54   ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-09 17:11     ` Derek Fawcus
2002-10-09 17:16     ` Pekka Savola
2002-10-09 21:46   ` Yuji Sekiya
2002-10-09 22:44     ` Derek Fawcus
2002-10-09 23:14       ` David S. Miller
2002-10-09 23:29         ` Derek Fawcus
2002-10-09 23:24           ` David S. Miller
2002-10-09 23:36             ` Derek Fawcus
2002-10-09 23:41             ` Yuji Sekiya
2002-10-09 23:45               ` David S. Miller
2002-10-10  0:00                 ` Yuji Sekiya
2002-10-10  0:04                   ` Derek Fawcus
2002-10-10  0:14                     ` Yuji Sekiya
2002-10-10  0:21                       ` Derek Fawcus
2002-10-10  0:35                         ` Yuji Sekiya
2002-10-10  0:42                           ` Derek Fawcus
2002-10-10  0:56                             ` Yuji Sekiya
2002-10-10  1:11                               ` Derek Fawcus [this message]
2002-10-10  0:10                   ` Derek Fawcus
2002-10-10  0:02                 ` Derek Fawcus
2002-10-09 23:51               ` Derek Fawcus

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=20021010021154.G8102@edi-view1.cisco.com \
    --to=dfawcus@cisco.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=sekiya@sfc.wide.ad.jp \
    --cc=usagi@linux-ipv6.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

all inboxes | Powered by JetHome®