From owner-freebsd-current Mon Feb 11 13:27:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 374E937B400 for ; Mon, 11 Feb 2002 13:27:25 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g1BLRKi09693; Mon, 11 Feb 2002 22:27:20 +0100 Received: (nullmailer pid 79227 invoked by uid 1000); Mon, 11 Feb 2002 16:01:31 -0000 Date: Mon, 11 Feb 2002 17:01:31 +0100 From: Mark Santcroos To: whoever Cc: freebsd-current@FreeBSD.ORG Subject: Re: Ethernet tunnel device Message-ID: <20020211170131.A79104@laptop.6bone.nl> References: <20020211032336.A2135@kashmir.etowns.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020211032336.A2135@kashmir.etowns.net>; from somebody@kashmir.etowns.net on Mon, Feb 11, 2002 at 03:23:36AM -0800 X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 11, 2002 at 03:23:36AM -0800, whoever wrote: > I am running FreeBSD current and barely got vmware > working on it. > Now I have another problem which I cant resolve. > If I close down the vmware program and restart I get an > error that vmnet(1,2,3,0 whatever) device is busy > and can not be used. > > using /usr/local/etc/rc.d/vmware.sh stop > and then start again didnt help either. > running ifconfig gave me the following > output (for vmnet2 which i was and intend to use again) > vmnet2: flags=8843 mtu 1500 > inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255 > inet6 fe80::2bd:fff:fe0f:2%vmnet2 prefixlen 64 scopeid 0x8 > ether 00:bd:0f:0f:00:02 > Opened by PID 698 > > clearly the device is opened by the previous > instance of the program and is not closed. > deleting the devices and recreating them didnt help any > (using devfs which comes stock in current - 5.0) > strangely even after deleting these devices from /dev > ifconfig still lists them !!!!!! may be its because of > devfs ....... but there ought to be someway. > > trying to destroy the device using ifconfig gives an error > too which (i believe) it should because destroy is not > for ethernet tunnel device if I am not wrong. > > but there are no options to destroy the ethernet tunnel > device in ifconfig .... Should there be????? > > I cant think anymore ... would appreciate input from you > guys . Any input. Please dont shy about telling me that > I am going the wrong ally Hi, I recently asked for this on mobile- if more people experienced this behaviour. I will be looking into this now I know more people have it. Monitor mobile@freebsd.org for updates on this. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message