netdev.vger.kernel.org archive mirror
 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 01:42:37 +0100	[thread overview]
Message-ID: <20021010014237.F8102@edi-view1.cisco.com> (raw)
In-Reply-To: <uofa39lm9.wl@sfc.wide.ad.jp>; from sekiya@sfc.wide.ad.jp on Thu, Oct 10, 2002 at 09:35:26AM +0900

On Thu, Oct 10, 2002 at 09:35:26AM +0900, Yuji Sekiya wrote:
> OK. I have assigned fe80:1910::10/64 link-local address to
> USAGI linux box and tried to ping ipv6.
> 
> Target IPv6 address: fe80:1910::10
> Repeat count [5]:
> Datagram size [100]:
> Timeout in seconds [2]:
> Extended commands? [no]:
> Output Interface: FastEthernet4/1
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to FE80:1910::10, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
> 
> Oct 10 09:27:35: IPV6: source FE80::201:64FF:FEA3:ED55 (local)
> Oct 10 09:27:35:       dest FE80:1910::10 (FastEthernet4/1)
> Oct 10 09:27:35:       traffic class 224, flow 0x0, len 64+16, prot 58, hops 255, originating
> Oct 10 09:27:35: IPv6: Sending on FastEthernet4/1

Well what do you know?  At least one implementation supports that type of
config.

Anyway,  I as said in an earlier email,  do whatever you want.  I just
considered that change to be dubious.

DF

  reply	other threads:[~2002-10-10  0:42 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
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 [this message]
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=20021010014237.F8102@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).