netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 19:20:54 +0100	[thread overview]
Message-ID: <1364408454.15362.1.camel@localhost> (raw)
In-Reply-To: <20130327181146.GB23223@order.stressinduktion.org>



On Wed, 2013-03-27 at 19:11 +0100, Hannes Frederic Sowa wrote:
> On Wed, Mar 27, 2013 at 04:37:53PM +0100, Wilco Baan Hofman wrote:
> > 
> > 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
> 
> In my test I didn't specify the local address so addr.s6_addr32[3]
> seems to be zero.  I'll have to search the RFCs why this is the case.

See section 3.7, rfc4213:

   The interface identifier [RFC3513] for such an interface may be based
   on the 32-bit IPv4 address of an underlying interface, or formed
   using some other means, as long as it is unique from the other tunnel
   endpoint with a reasonably high probability.

http://tools.ietf.org/html/rfc4213


-- Wilco

  reply	other threads:[~2013-03-27 18:21 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
2013-03-27 18:11     ` Hannes Frederic Sowa
2013-03-27 18:20       ` Wilco Baan Hofman [this message]
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=1364408454.15362.1.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).