From owner-freebsd-ports@FreeBSD.ORG Thu Apr 14 15:03:00 2005 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 00DF216A4CE for ; Thu, 14 Apr 2005 15:03:00 +0000 (GMT) Received: from excalibur.fbunet.de (excalibur.fbunet.de [80.190.243.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EDDD43D49 for ; Thu, 14 Apr 2005 15:02:59 +0000 (GMT) (envelope-from fbusse@gmx.de) Received: from artus.fbunet.de (port-212-202-40-81.dynamic.qsc.de [212.202.40.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by excalibur.fbunet.de (Postfix) with ESMTP id ACDEC19076; Thu, 14 Apr 2005 17:02:57 +0200 (CEST) Date: Thu, 14 Apr 2005 17:02:57 +0200 From: Fridtjof Busse To: delta@lackas.net Message-ID: <20050414150255.GA8129@artus.fbunet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.8i cc: ports@FreeBSD.org Subject: FreeBSD Port: vpnc-0.3.2_1 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: Thu, 14 Apr 2005 15:03:00 -0000 Hi I'd like to know if there are any plans to include the vpnc-wrapper [1] into the vpnc-port. It makes life much easier, especially in environments where you get a new nameserver after you've "entered" the VPN (such as at my university). The simple rc-script doesn't take care of this and thus makes it harder than necessary. Since the vpnc on linux can make use of resolvconf, I didn't notice the problem with the DNS at first. vpnc-wrapper would've helped :) [1] https://dragon.roe.ch/bitsnpieces/scripts/vpnc-wrapper -- Fridtjof Busse BOFH Excuse #333: A plumber is needed, the network drain is clogged