From owner-freebsd-net@FreeBSD.ORG  Thu Jun 26 20:39:06 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9B9AD1065686;
	Thu, 26 Jun 2008 20:39:06 +0000 (UTC)
	(envelope-from mgrooms@shrew.net)
Received: from shrew.net (206-223-169-85.beanfield.net [206.223.169.85])
	by mx1.freebsd.org (Postfix) with ESMTP id 611338FC1A;
	Thu, 26 Jun 2008 20:39:06 +0000 (UTC)
	(envelope-from mgrooms@shrew.net)
Received: from localhost (wm-ca.hub.org [206.223.169.82])
	by shrew.net (Postfix) with ESMTP id CB89079E2CA;
	Thu, 26 Jun 2008 15:39:05 -0500 (CDT)
Received: from shrew.net ([206.223.169.85])
	by localhost (mx1.hub.org [206.223.169.82]) (amavisd-new, port 10024)
	with ESMTP id 46582-09; Thu, 26 Jun 2008 20:39:05 +0000 (UTC)
Received: from hole.shrew.net (cpe-70-113-206-103.austin.res.rr.com
	[70.113.206.103]) by shrew.net (Postfix) with ESMTP id 547FA79E26A;
	Thu, 26 Jun 2008 15:39:05 -0500 (CDT)
Received: from hole.shrew.net (localhost [127.0.0.1])
	by hole.shrew.net (8.14.2/8.14.2) with ESMTP id m5QKd3m1055951;
	Thu, 26 Jun 2008 15:39:03 -0500 (CDT)
	(envelope-from mgrooms@shrew.net)
Received: (from www@localhost)
	by hole.shrew.net (8.14.2/8.14.2/Submit) id m5QKd3o7055950;
	Thu, 26 Jun 2008 15:39:03 -0500 (CDT)
	(envelope-from mgrooms@shrew.net)
X-Authentication-Warning: hole.shrew.net: www set sender to mgrooms@shrew.net
	using -f
To: Julian Elischer <julian@elischer.org>
MIME-Version: 1.0
Date: Thu, 26 Jun 2008 15:39:03 -0500
From: mgrooms <mgrooms@shrew.net>
Organization: Shrew Soft Inc
In-Reply-To: <4863F479.8010206@elischer.org>
References: <4863F479.8010206@elischer.org>
Message-ID: <b5e3d8444abd53fa34702646892abba8@localhost>
X-Sender: mgrooms@shrew.net
User-Agent: RoundCube Webmail/0.1-rc1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Cc: freebsd-net@freebsd.org, brooks@freebsd.org
Subject: Re: FreeBSD NAT-T patch integration
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mgrooms@shrew.net
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2008 20:39:06 -0000


On Thu, 26 Jun 2008 12:56:41 -0700, Julian Elischer <julian@elischer.org>
wrote:
> mgrooms wrote:
>>
>> I'm not trying to start a flame war here, but the patch has been
> floating
>> around since before the 5.x days. There just seems to be a dark cloud
>> hanging over it and I, and no doubt many others, really don't know why.
>> Please help us understand these reasons and what can be done to help.
> 

Woops. I meant to say that it had been floating around since before the 6.x
days. My bad.

> I'm planning on committing it unless someone can provide a reason not
> to, as I've seen it working, needed it, and have not seen any bad
> byproducts.
> 

I appreciate your offer to help. At the very least, I hope we will see a
published list of technical hurdles that need to be overcome before the
patch can be applied.

Thanks again,

-Matthew