From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: 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: Mon, 07 Oct 2002 11:55:30 -0700 (PDT) [thread overview]
Message-ID: <20021007.115530.00078126.davem@redhat.com> (raw)
In-Reply-To: <20021008.000559.17528416.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Tue, 08 Oct 2002 00:05:59 +0900 (JST)
Prefix length for link-local address should be 64, not 10.
This patch fixes prefix length of link-local address.
Following patch is against 2.4.19.
Patch is applied, thank you.
BTW, we start to run into conflicts now and most of USAGI patches now
I need to apply some parts by hand. Here is one example, with this
patch:
@@ -783,7 +783,7 @@
struct in6_addr addr;
ipv6_addr_set(&addr, __constant_htonl(0xFE800000), 0, 0, 0);
- addrconf_prefix_route(&addr, 10, dev, 0, RTF_ADDRCONF);
+ addrconf_prefix_route(&addr, 64, dev, 0, RTF_ADDRCONF);
}
static struct inet6_dev *addrconf_add_dev(struct net_device *dev)
Note in this hunk the __constant_htonl() which was transformed
to plain htonl() by already accepted USAGI patch.
It is not such a big deal now, but it may soon become larger as
bigger USAGI patches are applied. We will need to synchronize
at some point.
next prev parent reply other threads:[~2002-10-07 18:55 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 [this message]
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
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=20021007.115530.00078126.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.org \
--cc=yoshfuji@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).