From: Jan Oravec <jan.oravec@6com.sk>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] IPv6, sit: set prefix length 64 for link-local addresses
Date: Sun, 5 Oct 2003 11:18:45 +0200 [thread overview]
Message-ID: <20031005091844.GA23676@wsx.ksp.sk> (raw)
In-Reply-To: <20030926201953.3dfc67bf.davem@redhat.com>
Hello,
The mail with the patch was not delivered to netdev ML for some reasons.
Resending it..
The function sit_add_v4_addrs() calls ipv6_add_addr() with plen 64 if local
endpoint of tunnel is not configured, so I do not see a reason to set plen
to 128 if local endpoint is configured.
We are running patched kernel in our test-lab for about week and it is
working fine.
On Fri, Sep 26, 2003 at 08:19:53PM -0700, David S. Miller wrote:
> On Fri, 26 Sep 2003 19:54:05 +0200
> Jan Oravec <jan.oravec@6com.sk> wrote:
>
> > please apply the following patch.
> >
> > It sets the prefix length 64 instead of 128 for link-local addresses on sit interfaces.
>
> I've seen this patch before, and I remember it being rejected
> by other ipv6 developers.
>
> Do the USAGI or other folks remember what is going on here?
--- linux/net/ipv6/addrconf.c.orig 2003-09-08 21:50:29.000000000 +0200
+++ linux/net/ipv6/addrconf.c 2003-09-26 19:37:27.000000000 +0200
@@ -1681,7 +1681,7 @@
}
if (addr.s6_addr32[3]) {
- ifp = ipv6_add_addr(idev, &addr, 128, scope, IFA_F_PERMANENT);
+ ifp = ipv6_add_addr(idev, &addr, 64, scope, IFA_F_PERMANENT);
if (!IS_ERR(ifp)) {
spin_lock_bh(&ifp->lock);
ifp->flags &= ~IFA_F_TENTATIVE;
Best Regards,
--
Jan Oravec
6COM s.r.o.
http://www.6com.sk
next prev parent reply other threads:[~2003-10-05 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030926175405.GA31498@wsx.ksp.sk>
2003-09-27 3:19 ` [PATCH] IPv6, sit: set prefix length 64 for link-local addresses David S. Miller
2003-10-05 9:18 ` Jan Oravec [this message]
2003-10-05 12:28 ` YOSHIFUJI Hideaki / 吉藤英明
2003-10-05 12:35 ` Jan Oravec
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=20031005091844.GA23676@wsx.ksp.sk \
--to=jan.oravec@6com.sk \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--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).