From owner-freebsd-net  Mon Aug 16 23:22:30 1999
Delivered-To: freebsd-net@freebsd.org
Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73])
	by hub.freebsd.org (Postfix) with ESMTP id 2D9BB14E0D
	for <freebsd-net@freebsd.org>; Mon, 16 Aug 1999 23:21:32 -0700 (PDT)
	(envelope-from Chris@aims.com.au)
Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.0.2])
	by postoffice.aims.com.au (8.9.3/8.9.3) with ESMTP id QAA00538
	for <freebsd-net@freebsd.org>; Tue, 17 Aug 1999 16:21:55 +1000 (EST)
	(envelope-from Chris@aims.com.au)
Received: from nts-ts1 by aims.com.au
	with SMTP (MDaemon.v2.84.R)
	for <freebsd-net@freebsd.org>; Tue, 17 Aug 1999 16:18:46 +1000
From: "Chris Knight" <chris@aims.com.au>
To: <freebsd-net@freebsd.org>
Cc: <pb@fasterix.freenix.org>
Subject: pipsecd
Date: Tue, 17 Aug 1999 16:18:45 +1000
Message-ID: <001d01bee878$5cea4890$0200a8c0@nts-ts1.aims.private>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal
X-MDaemon-Deliver-To: freebsd-net@freebsd.org
X-Return-Path: Chris@aims.com.au
Reply-To: chris@aims.com.au
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Howdy,
	I've just noticed that pipsecd has appeared in the ports tre. Does anyone
know how to use it?

	On machine A, I have in my pipsecd.conf:

      sa ipesp spi=1000 enc=blowfish_cbc ekey=<key for B> dest=<machine B
public IP>
      sa ipesp spi=1001 enc=blowfish_cbc ekey=<key for A>
      if /dev/tun1 local_spi=1001 remote_spi=1000

	On machine B, I have in my pipsecd.conf:

      sa ipesp spi=1000 enc=blowfish_cbc ekey=<key for B>
      sa ipesp spi=1001 enc=blowfish_cbc ekey=<key for A> dest=<machine A
public IP>
      if /dev/tun1 local_spi=1000 remote_spi=1001

	On machine A, I add:
	ifconfig tun1 192.168.3.1 192.168.3.2 netmask 0xffffff00 mtu 1440

	On machine B, I add:
      ifconfig tun1 192.168.3.2 192.168.3.1 netmaks 0xffffff00 mtu 1440

	The update probes are sent and received, but pinging the remote end of the
tun1 device sends the packet via my default route.
	What am I doing wrong?

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message