From owner-freebsd-isp Mon Apr 9 15: 2:24 2001 Delivered-To: freebsd-isp@freebsd.org Received: from finch.netops.mindspring.net (finch.netops.mindspring.net [207.69.180.46]) by hub.freebsd.org (Postfix) with ESMTP id 9AF8837B422 for ; Mon, 9 Apr 2001 15:02:18 -0700 (PDT) (envelope-from echo.ranger@corp.earthlink.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by finch.netops.mindspring.net (Postfix) with ESMTP id E30505D83 for ; Mon, 9 Apr 2001 18:02:17 -0400 (EDT) Date: Mon, 9 Apr 2001 18:02:17 -0400 (EDT) From: Michael Proto X-Sender: To: Subject: Windows IPSec clients that interface well with KAME? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm currently investigating replacing our current remote-access solution with the KAME kit included with FreeBSD 4.x. I'm having problems finding Windows client software that is fully IPSec-compliant. Lately, I've found a few pieces of client software (like VPNet's client, for example) that claim to be IPSec compliant, yet they require propritary hardware/software for various other things (like configuring the client software, for example). Ultimately, I'm looking for some software like SafeNet that doesn't require any propritary equipement and will connect to a FreeBSD KAME-equipped server in transport mode. The method of keying (manual vs. racoon) doesn't matter. Anyone have any sure-fire programs they've gotten to work? Thanks, Michael Proto -- Michael Proto | echo.ranger@corp.earthlink.net Security Engineer, EarthLink Inc. | (404)815-0770 x22114 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message