From: Wilco Baan Hofman <wilco@baanhofman.nl>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org
Subject: Re: /128 link-local subnet on 6in4 (sit) tunnels?
Date: Wed, 27 Mar 2013 16:37:53 +0100 [thread overview]
Message-ID: <1364398673.21709.4.camel@localhost> (raw)
In-Reply-To: <20130327151210.GA23223@order.stressinduktion.org>
On Wed, 2013-03-27 at 16:12 +0100, Hannes Frederic Sowa wrote:
> On Tue, Mar 26, 2013 at 11:04:17PM +0100, Wilco Baan Hofman wrote:
> > So I was wondering, is there any particular reason for the use of a /128
> > link-local or is this just a bug?
>
> Can you show me the commands how you set up the tunnel. It does create /64 ll
> with embedded ipv4 addresses for me here on v3.8.
>
Weird, but sure, here goes:
ip tunnel add tunv6-uplink1 mode sit remote 192.168.1.1 local
192.168.1.21
ip link set tunv6-uplink1 up mtu 1472
Also, this patch seems to fix it:
--- linux-3.8.3.orig/net/ipv6/addrconf.c
+++ linux-3.8.3/net/ipv6/addrconf.c
@@ -2487,7 +2487,7 @@ static void sit_add_v4_addrs(struct inet
}
if (addr.s6_addr32[3]) {
- add_addr(idev, &addr, 128, scope);
+ add_addr(idev, &addr, 64, scope);
return;
}
-- Wilco
next prev parent reply other threads:[~2013-03-27 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 22:04 /128 link-local subnet on 6in4 (sit) tunnels? Wilco Baan Hofman
2013-03-27 15:12 ` Hannes Frederic Sowa
2013-03-27 15:37 ` Wilco Baan Hofman [this message]
2013-03-27 18:11 ` Hannes Frederic Sowa
2013-03-27 18:20 ` Wilco Baan Hofman
2013-03-27 18:35 ` Hannes Frederic Sowa
2013-03-27 19:12 ` Wilco Baan Hofman
2013-03-28 13:00 ` Wilco Baan Hofman
2013-03-28 13:12 ` Hannes Frederic Sowa
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=1364398673.21709.4.camel@localhost \
--to=wilco@baanhofman.nl \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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).