Date: Tue, 17 Aug 1999 16:18:45 +1000 From: "Chris Knight" <chris@aims.com.au> To: <freebsd-net@freebsd.org> Cc: <pb@fasterix.freenix.org> Subject: pipsecd Message-ID: <001d01bee878$5cea4890$0200a8c0@nts-ts1.aims.private>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001d01bee878$5cea4890$0200a8c0>