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 01:04:39 +0100 [thread overview]
Message-ID: <20021010010439.C8102@edi-view1.cisco.com> (raw)
In-Reply-To: <ur8ez9n8d.wl@sfc.wide.ad.jp>; from sekiya@sfc.wide.ad.jp on Thu, Oct 10, 2002 at 09:00:34AM +0900
On Thu, Oct 10, 2002 at 09:00:34AM +0900, Yuji Sekiya wrote:
> At Wed, 09 Oct 2002 16:45:04 -0700 (PDT),
> ** David S. Miller <davem@redhat.com> wrote:
>
> > The reason we change the prefix length from /10 to /64 is
> > following spec and adapting other imprementations.
> >
> > I think Derek's explanation shows that the specification
> > allows the /10 behavior.
>
> Hmm... we interpret the spec as /64 prefix.
>
> > Also, I suspect that since Derek works for Cisco, some "other
> > implementations" behave how he describes. :-)
>
> I have cisco box which installed IPv6 IOS.
> But it defines no prefix length at an interface,
>
> FastEthernet4/1 is up, line protocol is up
> IPv6 is enabled, link-local address is FE80::201:64FF:FEA3:ED55
>
> and outgoing interface of routing table is NULL ? :-)
>
> L FE80::/10 [0/0]
> via ::, Null0, 7w0d
Turn on 'debug ipv6 nd', 'debug ipv6 icmp', 'debug ipv6 pack d'
Then do 'ping ipv6' specify a link local of say fe80:1910::10 and
an egress interface, and watch what happens.
DF
next prev parent reply other threads:[~2002-10-10 0:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 15:05 [PATCH] IPv6: Fix Prefix Length of Link-local Addresses 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 19:03 ` kuznet
2002-10-09 19:23 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-09 20:47 ` kuznet
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 [this message]
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
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=20021010010439.C8102@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;
as well as URLs for NNTP newsgroup(s).