From owner-freebsd-arch@FreeBSD.ORG Fri Jun 16 21:21:38 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09F0C16A484 for ; Fri, 16 Jun 2006 21:21:38 +0000 (UTC) (envelope-from sullrich@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3AA243D64 for ; Fri, 16 Jun 2006 21:21:31 +0000 (GMT) (envelope-from sullrich@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so29566uge for ; Fri, 16 Jun 2006 14:21:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QNdmAY6uaOMRV4xX9vi4O5mALyKCmc9B41W9yBR+ohUc08gDE6w9g/7EAtviHUQaBFQJ7sZ6F2x4HoHJojj5Sj7QoYYqwFM8rwmXCy9krvz5Dzvv3NWlrrGJO51eHlHKTsAWKlavev48TA9aG747PmhFjGgXD1qEG1mmpLg7Bos= Received: by 10.67.30.6 with SMTP id h6mr2859112ugj; Fri, 16 Jun 2006 08:41:27 -0700 (PDT) Received: by 10.67.28.14 with HTTP; Fri, 16 Jun 2006 08:41:27 -0700 (PDT) Message-ID: Date: Fri, 16 Jun 2006 11:41:27 -0400 From: "Scott Ullrich" To: "Max Laier" In-Reply-To: <200606161735.33801.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060615225312.GB64552@heff.fud.org.nz> <200606161735.33801.max@love2party.net> Cc: freebsd-net@freebsd.org, net@freebsd.org, Andrew Thompson , arch@freebsd.org Subject: Re: enc0 patch for ipsec X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2006 21:21:38 -0000 On 6/16/06, Max Laier wrote: > I think it should get a "device enc" on its own. Some people might consider > enc(4) to be a security problem so getting it with FAST_IPSEC automatically > isn't preferable. You have to specifically create the enc0 interface (ifconfig enc0 create) before it becomes active. Otherwise it will not hit the enc code path unless the device is created. Scott