l2tp support on OS's Re: [v6tc] Re: Tunneling and Transition Drafts

Jeroen Massar <jeroen@unfix.org> Fri, 08 April 2005 21:18 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13207; Fri, 8 Apr 2005 17:18:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK10s-0007DS-V8; Fri, 08 Apr 2005 17:27:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DK0pr-0004Rp-TJ; Fri, 08 Apr 2005 17:16:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DK0pq-0004RU-Cf for v6tc@megatron.ietf.org; Fri, 08 Apr 2005 17:16:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13090 for <v6tc@ietf.org>; Fri, 8 Apr 2005 17:16:12 -0400 (EDT)
Received: from 213-136-24-43.adsl.bit.nl ([213.136.24.43] helo=purgatory.unfix.org ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK0ye-00076J-O6 for v6tc@ietf.org; Fri, 08 Apr 2005 17:25:22 -0400
Received: from firenze.zurich.ibm.com (pat.zurich.ibm.com [195.176.20.45]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by purgatory.unfix.org (Postfix) with ESMTP id B5CE28880; Fri, 8 Apr 2005 23:15:59 +0200 (CEST)
Subject: l2tp support on OS's Re: [v6tc] Re: Tunneling and Transition Drafts
From: Jeroen Massar <jeroen@unfix.org>
To: "W. Mark Townsley" <townsley@cisco.com>
In-Reply-To: <4256D9D2.9070604@cisco.com>
References: <200504081806.j38I6Z1M013207@givry.rennes.enst-bretagne.fr> <1112984642.1788.15.camel@firenze.zurich.ibm.com> <4256D9D2.9070604@cisco.com>
Organization: Unfix
Date: Fri, 08 Apr 2005 23:15:56 +0200
Message-Id: <1112994956.1788.37.camel@firenze.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: "v6tc@ietf.org" <v6tc@ietf.org>
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2009918115=="
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86

Short summary first, what supports it:
 - Windows XP SP2 does not have it
 - Windows Longhorn will have it (they say),
   but out in 2007 or most likely later and then needs to be deployed
   and be fed to the users, who will stick with XP for some time anyway.
 - *BSD
 - Linux
 - Most CPE's (Cisco/Yahama/...)

But Windows is a huge market for most ISP's...

On Fri, 2005-04-08 at 15:21 -0400, W. Mark Townsley wrote:
> 
> Jeroen Massar wrote:
> > 
> > Nevertheless I'll put it somewhere on that big list, lets see how many parties
> > get canceled this week...
> 
> I think a decent GPL or free IPv6 PPP for Windows XP would be a service to the 
> community in general. Please write one.

Some other people convinced me and I actually was under the impression
that L2TP would not work over NAT thus I need to make up for it. It also
allows quite a number of scenarios to be solved more easily.
I don't really like GPL but that is off topic for sure. Well the night
reading is printed out ;) <hint> Let's make L2TP a viable option.

> >>In the end, a lot of implementations may actually be CPEs rather than hosts, in 
> >>which case having the linux implementation helps.
> > 
> > 
> > Linux supports it, but not too many people want to actually touch their gear.
> > and for most of those people Linux is still scary.
> 
> For a CPE? Linksys uses Linux.

I know, but I meant the original image, as customers might still be
holding back on using a non-vendor image. It would thus be really nice
to have images that defaultly are IPv6 enabled, and I mean this for
*all* the products that are available.

The OpenWRT images, with which I flashed my box, indeed support IPv6 and
getting a lt2p client/daemon on it should not be an issue indeed.

Greets,
 Jeroen

_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc