From owner-freebsd-hackers Mon Sep 28 16:10:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18436 for freebsd-hackers-outgoing; Mon, 28 Sep 1998 16:10:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18418 for ; Mon, 28 Sep 1998 16:10:47 -0700 (PDT) (envelope-from jflowers@ezo.net) Received: from violet.ezo.net (violet.ezo.net [206.102.130.133]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id TAA02918; Mon, 28 Sep 1998 19:10:24 -0400 (EDT) From: "Jim Flowers" To: "Stephanie Wehner" , Subject: Re: IPsec for ipv4 Date: Mon, 28 Sep 1998 19:11:49 -0400 Message-ID: <01bdeb35$5f037ca0$858266ce@violet.ezo.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. That'll do it. So far I've a host to host connection on a single link with freebsd on one host and openbsd on another host. Seems quite straight-forward. Now on to a tunnel. -----Original Message----- From: Stephanie Wehner To: freebsd-hackers@FreeBSD.ORG Date: Monday, September 28, 1998 12:52 PM Subject: Re: IPsec for ipv4 >: Did just fine until I got to tools/complete/photurisd/kernel.c. No >: declarations for IP_SEC_LEVEL_BYPASS, IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL or >: IP_ESP_NETWORK_LEVEL. Same thing in openbsd source. Are these just not >: important? > >Look into netinet/in.h > >bye, >Stephanie >----------------------------<> _@r4k.net <>-----------------<> FreeBSD <>--- > "I had to hit him -- he was starting to make sense." > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message