From owner-freebsd-security@FreeBSD.ORG Wed May 7 19:21:58 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70D5037B401 for ; Wed, 7 May 2003 19:21:58 -0700 (PDT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D2D143F85 for ; Wed, 7 May 2003 19:21:55 -0700 (PDT) (envelope-from metrol@metrol.net) Received: from metlap (adsl-67-121-60-9.dsl.anhm01.pacbell.net [67.121.60.9]) h482LsPg090964 for ; Wed, 7 May 2003 22:21:54 -0400 From: Michael Collette To: FreeBSD Security Date: Wed, 7 May 2003 19:21:33 -0700 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305071921.33596.metrol@metrol.net> Subject: VPN through BSD for Win2k, totally baffled X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2003 02:21:58 -0000 Scenario: FreeBSD box running IPFW acting as a gateway to private network. The private network is made up of entirely routeable IP addresses. External users running Win2k and XP on DSL connections with dynamic IPs. Goal: To have the FreeBSD gateway securely authenticate and encrypt the traffic between the outside users and the internal network. I've spent the last 3 days running up and down Google and reading any books that approach the subject of setting up a VPN. The further down this road I've travelled the more confused I am. I assume the following: * Need to have a certificate setup with OpenSSL. * Racoon needs to deal with a key exchange. * Some kind of tunneling gets put into play. * Setkey needs appropriate policies. I happened across the Google cache of a tutorial that seems to cover this subject. There seems to be a couple of key points missing, as well as some apparently out of date syntax. I did manage to create a CA and client cert from a mix of this tutorial and the AbsoluteBSD book. http://216.239.37.104/search?q=cache:mFG0kB-ghLoC:www.sigsegv.cx/FreeBSD-WIN2K-IPSEC-HOWTO-2.html+FreeBSD-WIN2K-IPSEC-HOWTO-2.html&hl=en&lr=lang_en&ie=UTF-8 Managed to get a certificate generated from that process installed on a test XP box per the following... http://216.239.33.104/search?q=cache:FFxjH0VQGD0C:www.sigsegv.cx/FreeBSD-WIN2K-IPSEC-HOWTO-4.html+FreeBSD-WIN2K-IPSEC-HOWTO-4.html&hl=en&lr=lang_en&ie=UTF-8 Where I totally lost it was on the FreeBSD setup. The author is referring to certificates that he never described how they should be created. I didn't know what in the heck to do here. http://216.239.33.104/search?q=cache:oNMJe4EHOu4C:www.sigsegv.cx/FreeBSD-WIN2K-IPSEC-HOWTO-3.html+FreeBSD-WIN2K-IPSEC-HOWTO-3.html&hl=en&lr=lang_en&ie=UTF-8 Am I even on the right path? Aside from this one tutorial I've been through several others, as well as looking at a variety of IPSec related pages. There's obviously a number of different approaches out there to take, but I'm simply looking for one that works. Just to know that I'm heading in the correct direction or not would be an incredible help. Thanks, -- "Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read." - Groucho Marx