From owner-freebsd-questions@FreeBSD.ORG Sun Dec 16 19:47:32 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 809DDF0E for ; Sun, 16 Dec 2012 19:47:32 +0000 (UTC) (envelope-from fred@antre.fperrin.net) Received: from mail.fperrin.net (mail.fperrin.net [IPv6:2001:41d0:2:2be3::25]) by mx1.freebsd.org (Postfix) with ESMTP id 1728C8FC1F for ; Sun, 16 Dec 2012 19:47:31 +0000 (UTC) Received: from antre.fperrin.net (antre.priv.fperrin.net [IPv6:fd93:c8e5:9cb3:666::22]) by mail.fperrin.net (Postfix) with ESMTP id 84F43173 for ; Sun, 16 Dec 2012 20:47:29 +0100 (CET) Received: (from fred@localhost) by antre.fperrin.net (8.14.5/8.14.5/Submit) id qBGJlTid023219; Sun, 16 Dec 2012 20:47:29 +0100 (CET) (envelope-from fred) From: =?utf-8?Q?Fr=C3=A9d=C3=A9ric_Perrin?= To: freebsd-questions@freebsd.org Subject: Re: IPv6in4 tunnel with only one /64 prefix Organization: =?utf-8?Q?R=C3=A9seau?= des =?utf-8?B?w4lsw6h2ZXM=?= References: <86bof9yuqt.fsf@antre.fperrin.net> Date: Sun, 16 Dec 2012 20:47:29 +0100 In-Reply-To: <86bof9yuqt.fsf@antre.fperrin.net> (=?utf-8?B?IkZyw6lkw6ly?= =?utf-8?B?aWM=?= Perrin"'s message of "Wed, 07 Nov 2012 22:21:30 +0100") Message-ID: <86sj75g4oe.fsf@antre.fperrin.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2012 19:47:32 -0000 Following-up on myself... Of course Steve's suggestion was not what I wanted to hear, as I wanted to do stuff myself :) The take-away is that my plan works. I have a full write up in French at ; I can translate into English if people are interested. Basically, you need to tell the external interface that it is not in a /64 addres, then you can add the routes you need. There is nothing special to do on the router at the other end of the tunnel, except turning on the DHCPv6 server. I did have to setup an NDP proxy, the (quite trivial) code is at . I did hit a bug in ISC dhclient. There is a fix in the Debian bug tracker (a similar fix in Network Manager for desktop systems already made itinto their git). Le mercredi 7 =C3=A0 22:21, Fr=C3=A9d=C3=A9ric Perrin a =C3=A9crit : > Hello list, > > I have a FreeBSD server with native IPv6 connectivity. At home, my ISP > provides me with only IPv4 connectivity. In order to get IPv6 to the > home, I had the idea of creating a 6in4 tunnel between my home gateway > and my FreeBSD server. The part about creating the tunnel, routing > between the home and the server works using private addresses (fc00::/8 > over gif0). > > However, I only have one global /64 on the FreeBSD box. What can I do? > > I have the idea of subnetting the /64 into e.g. /80, route a couple of > /80s through gif to the home and use another /80 for the FreeBSD server. > However, as the router into which my FreeBSD server is connected will > expect the entire /64 to be directly connected, I will have to setup > some kind of NDP proxy for the /80 to the home. I will also lose > autoconf, but I can live with that. > > Comments, either on the plan above, or something else I haven't thought > of? --=20 Fred