From owner-freebsd-net@FreeBSD.ORG  Tue Mar 24 20:01:23 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2529B1065692;
	Tue, 24 Mar 2009 20:01:23 +0000 (UTC)
	(envelope-from qing.li@bluecoat.com)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28])
	by mx1.freebsd.org (Postfix) with ESMTP id 061CE8FC26;
	Tue, 24 Mar 2009 20:01:22 +0000 (UTC)
	(envelope-from qing.li@bluecoat.com)
Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95])
	by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n2OK1L5D028612;
	Tue, 24 Mar 2009 13:01:22 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Mar 2009 13:01:12 -0700
Message-ID: <B583FBF374231F4A89607B4D08578A43039B2E9A@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Problems with inward PPTP tunnel
Thread-Index: AcmsdCAmcSePkMgmR/K27LxG4dkPKwARFbtw
References: <200903222114.PAA17884@lariat.net>
	<87153F88702C4FBCA3FC799082960C45@adnote989>
	<B583FBF374231F4A89607B4D08578A4303928C88@bcs-mail03.internal.cacheflow.com>
	<5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Luiz Otavio O Souza" <lists.br@gmail.com>
Cc: Brett Glass <brett@lariat.net>, Qing Li <qingli@freebsd.org>,
	net@freebsd.org
Subject: RE: Problems with inward PPTP tunnel
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Tue, 24 Mar 2009 20:01:27 -0000

>=20
> Yes i've read your patch, but i don't understand what you are
meaning...
> and yes, changing the definition of rt_Update is not my first
intention,
> but it is the way i've found to fix this.
>=20
> Backing to the patch... The rt_Update need the ifp and ifa information
> to correctly update the route, and this is available only in
> route_UpdateMTU (wich read the current route table).
>=20
> You are suggesting that this information could be found at
> sa[RTAX_GATEWAY] (if sa[RTAX_GATEWAY]->sa_family =3D=3D AF_LINK) ? And =
i=20
> don't need to pass the sa[RTAX_IFP] and sa[RTAX_IFA] ?
>=20

Yes. The concept should be similar to the handling code for route
insertion=20
where one does, e.g.:

	route add -net a.b.c.d/24 -iface em0

Joe Marcus verified my patch in his environment. My suggestion is for
you
to try it out and see if that patch also fixes whatever problem that you
are=20
running into.

Thanks,

-- Qing