From owner-freebsd-net@FreeBSD.ORG Mon Jul 28 03:27:10 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D62CB37B401 for ; Mon, 28 Jul 2003 03:27:10 -0700 (PDT) Received: from cell.sick.ru (cell.sick.ru [195.91.162.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD18E43F75 for ; Mon, 28 Jul 2003 03:27:09 -0700 (PDT) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.6/8.12.8) with ESMTP id h6SAR7Nx065496 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Jul 2003 14:27:08 +0400 (MSD) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.6/8.12.6/Submit) id h6SAR7MK065495; Mon, 28 Jul 2003 14:27:07 +0400 (MSD) Date: Mon, 28 Jul 2003 14:27:07 +0400 From: Gleb Smirnoff To: Brett Glass Message-ID: <20030728102707.GB65369@cell.sick.ru> References: <20030723213028.GB48101@sunbay.com> <4.3.2.7.2.20030723192331.02c9bbd0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030723192331.02c9bbd0@localhost> User-Agent: Mutt/1.5.1i cc: net@freebsd.org Subject: Re: NAT and PPTP X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2003 10:27:11 -0000 On Wed, Jul 23, 2003 at 07:27:38PM -0600, Brett Glass wrote: B> I haven't gotten any hopes up, but it would be nice. It seems as B> if the only alternatives are to un-GNU PoPToP (which requires B> a clean room team; possible but not easy) or to create a FreeBSD B> pptpd that is analogous to pppoed. This would use your work, Archie, IMHO, this is not good idea. Currently I'm running two different types of access points: 1) PPPoE concentrators: pppoed + ppp 2) PPTP server: mpd with huge mpd.conf and mpd.links As I remember, Brett said that mpd allocates a number of nodes for each connection in kernel memory. That's right. But in case of pppoed+ppp or imaginary pptpd+ppp you will have a user-level process and ng_socket for each connection. Not shure that it will take less memory. But it will do a lot of context switching. On my own experience it looks like PPTP (no comperssion, no encryption) access point with mpd is more robust than PPPoE one with pppoed+ppp. Currently I'm planning to look into Alexandr Motin's patches giving PPPoE server support for mpd. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE