From owner-freebsd-net@FreeBSD.ORG Tue Mar 24 16:02:10 2009 Return-Path: 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 12737106566C for ; Tue, 24 Mar 2009 16:02:10 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.119.58.2]) by mx1.freebsd.org (Postfix) with ESMTP id 922148FC27 for ; Tue, 24 Mar 2009 16:02:09 +0000 (UTC) (envelope-from brett@lariat.net) Received: from anne-o1dpaayth1.lariat.org (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id KAA20824; Tue, 24 Mar 2009 10:02:02 -0600 (MDT) Message-Id: <200903241602.KAA20824@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 24 Mar 2009 10:01:40 -0600 To: "Luiz Otavio O Souza" , "Li, Qing" From: Brett Glass In-Reply-To: <5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989> References: <200903222114.PAA17884@lariat.net> <87153F88702C4FBCA3FC799082960C45@adnote989> <5E03C21CD6544D23B4E4A61E85C7E2C8@adnote989> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 16:02:13 -0000 At 05:31 AM 3/24/2009, Luiz Otavio O Souza wrote: >>Hi, >> >>I read over your patch and I don't think you need to >>change the definition of rt_Update() to fix this bug. >> >>Have you read my patch committed to head/user.sbin/ppp/route.c >>on 12/18/2008? svn r186308, cvs r1.96. >> >>Please take a look. >> >>Thanks, >> >>-- Qing > >Hi Qing, > >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. > >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). > >You are suggesting that this information could be found at >sa[RTAX_GATEWAY] (if sa[RTAX_GATEWAY]->sa_family == AF_LINK) ? And >i don't need to pass the sa[RTAX_IFP] and sa[RTAX_IFA] ? > >Well, i really don't remember, but i'll check and post an update later. > >Thanks, >Luiz I personally think that, from a style perspective, changing the definition of rt_Update is good. I was thinking of doing it myself when I was inspecting the code and trying to figure out how to ensure that the interface was specified in the routing table entry. Adding the additional arguments makes the routine more flexible and makes the intent of calls to it more explicit. That being said, any change that fixes the bug is welcome. (The code that shipped with 7.1-RELEASE will break many if not most systems that rely on userland PPP to implement a server.) I might consider using mpd instead, but it would be a big implementation change and mpd lacks a few capabilities that I really need. --Brett Glass