From owner-freebsd-current  Wed Sep 12 18:41:33 2001
Delivered-To: freebsd-current@freebsd.org
Received: from owa-sj-1.digisle.com (owa-sj-1.digisle.com [167.216.153.124])
	by hub.freebsd.org (Postfix) with ESMTP id 614B337B406
	for <freebsd-current@freebsd.org>; Wed, 12 Sep 2001 18:41:31 -0700 (PDT)
Received: from VWALL-SJ-1.digisle.com ([167.216.153.118]) by owa-sj-1.digisle.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 12 Sep 2001 18:42:41 -0700
Received: from 206.220.227.145 by VWALL-SJ-1.digisle.com (InterScan E-Mail VirusWall NT); Wed, 12 Sep 2001 18:41:40 -0700
Message-ID: <3BA00ECA.5D311DB9@digisle.net>
Date: Wed, 12 Sep 2001 18:41:30 -0700
From: Maksim Yevmenkin <myevmenk@digisle.net>
Organization: Digital Island
X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Brooks Davis <brooks@one-eyed-alien.net>
Cc: Doug Ambrisko <ambrisko@ambrisko.com>,
	freebsd-current@FreeBSD.ORG
Subject: Re: Anyone experience problems with the "tap" device in current?
References: <200109122359.f8CNxHg59969@ambrisko.com> <20010912172759.A31013@Odin.AC.HMC.Edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Sep 2001 01:42:41.0585 (UTC) FILETIME=[608B4210:01C13BF5]
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Brooks Davis wrote:
> 
> On Wed, Sep 12, 2001 at 04:59:16PM -0700, Doug Ambrisko wrote:
> > I just tried using tap in current.  In both cases I don't see the
> > /dev/tapX devices with devfs and accessing it without devfs doesn't
> > work reporting "Device not configured".  I tried it as a module and
> > built into the kernel.  Does anyone have this working?
> 
> With devfs, you just need to try opening the device and you'll get it if
> it's not busy.  You can also open /dev/tap and get an arbitrary one.
> This is due to tun(4) style cloning code I committed recently.  I'm not
> actually sure this is the way we want to handle cloning hybrid devices,
> but there is precident so I committed the patch.  I think we may want to
> move to a model were we use interface cloning rather then devfs cloning
> because it will work in stable.

just cvsup'ed new sources and compiled/installed new kernel.
everything seems to work fine. at least without DEVFS. i will
do full buildword tomorrow and test more.

thansk,
max

p.s. building DEVFS enabled kernel now....

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