From owner-freebsd-ports@FreeBSD.ORG Mon Jan 5 04:14:25 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58231106566B for ; Mon, 5 Jan 2009 04:14:25 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 362838FC1A for ; Mon, 5 Jan 2009 04:14:25 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n054EOfJ048908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 4 Jan 2009 20:14:24 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n054EONj048907 for freebsd-ports@freebsd.org; Sun, 4 Jan 2009 20:14:24 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA10833; Sun, 4 Jan 09 20:13:04 PST Date: Sun, 04 Jan 2009 20:15:26 -0800 From: perryh@pluto.rain.com To: freebsd-ports@freebsd.org Message-Id: <4961895e.WTyxsPUoWe//+h++%perryh@pluto.rain.com> References: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> In-Reply-To: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: FIXED: vpnc connects, but does not work X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 04:14:25 -0000 > I have installed vpnc to connect to an employer's Cisco VPN > system, and it seems to make the connection, but after connecting > I can't ping the gateway nor anything beyond it ... It turned out the only problem was the absence of NAT Traversal Mode cisco-udp in vpnc.conf. (Presumably not all configurations of the Cisco 3000 will need that, else it would be the default, but it seems to be correct for the one involved here.) I never did figure out why that kept the interface from responding to a ping of its own address :(