From owner-freebsd-ports@FreeBSD.ORG Sun Jul 13 22:11:01 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E789237B401 for ; Sun, 13 Jul 2003 22:11:01 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 396AA43F93 for ; Sun, 13 Jul 2003 22:11:01 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.org (8.9.3/8.9.3) id XAA05369 for ports@freebsd.org; Sun, 13 Jul 2003 23:10:57 -0600 (MDT) Date: Sun, 13 Jul 2003 23:10:57 -0600 (MDT) From: Brett Glass Message-Id: <200307140510.XAA05369@lariat.org> To: ports@freebsd.org Subject: Requested change to "poptop" port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 05:11:02 -0000 I'm running a PPTP server that uses the net/poptop port, and need the ability to use different PPP configurations when users tunnel in via different interfaces. I've hit upon the idea of using multiple instances of the daemon, listening on different addresses, which fire off userland PPP using different labels within the ppp.conf file. Unfortunately, the port doesn't currently have the ability to do this, nor can it select a different PPP configuration file when it invokes userland PPP. I'd therefore like to request that the -o option be changed so that, instead of specifying an options file for PPP, it specifies the system label to be used when PPP is invoked. I can't look at the PoPToP code myself, because it's GPLed, but a friend who does Linux hacking did it for me as a favor. He tells me that the change mostly involves REMOVING code -- specifically, a few lines that test for the presence of a file that's specified with the -o option under Linux. He says that invoking PPP with that option as the system label (or with "pptp" as the label if something different isn't specified) is likewise trivial. Could the port maintainer make this change to the port? --Brett Glass