From owner-freebsd-current@freebsd.org Tue Nov 3 00:17:05 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6551DA25B05 for ; Tue, 3 Nov 2015 00:17:05 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id C5C22145D for ; Tue, 3 Nov 2015 00:17:04 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 65299 invoked by uid 89); 2 Nov 2015 23:50:21 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.180.132) by mail.grem.de with ESMTPA; 2 Nov 2015 23:50:21 -0000 Date: Tue, 3 Nov 2015 00:50:19 +0100 From: Michael Gmelin To: Craig Rodrigues Cc: George Neville-Neil , Randall Stewart , Alfred Perlstein , freebsd-current Current Subject: Re: Tunnelling IPv4 over IPv6 for GitHub access? Message-ID: <20151103005019.4250d920@bsd64.grem.de> In-Reply-To: References: X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 00:17:05 -0000 On Mon, 2 Nov 2015 14:04:18 -0800 Craig Rodrigues wrote: > Hi, > > I have some machines which are on an IPv6 only network. > It works great and I can access most things on the IPv6 Internet > that I need like Google ( [2607:f8b0:4004:808::1014]) , Facebook > ([2a03:2880:1010:df05:face:b00c:0:2]), CNN ( [2620:100:e000::8001]), > etc. > > However, the one thing I cannot access is GitHub, which does not > support IPv6 (!!!!). > > Is there a way that I can tunnel IPv4 over an IPv6 network? > > I read this blog post: > http://www.aisecure.net/2013/02/03/tunneling-ipv4-over-ipv6-vpn/ > and wasn't sure if this was an approach that I could use. ikvjwd.com once offered a service using haproxy, you can find their configuration here: https://github.com/rcsheets/ikvjwd/commit/58979dcaf42fbbd9203067a6ba4629ba01469120 Another way to tunnel all IPv4 traffic is set up an OpenVPN server on a dual stack machine and route your client IPv4 traffic over it (that approach is actually very easy to accomplish, stable and will work with any service). - Michael > > -- > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- Michael Gmelin