From owner-freebsd-ports Wed Jul 12 7:15:44 2000 Delivered-To: freebsd-ports@freebsd.org Received: from drmemory.fnal.gov (drmemory.fnal.gov [131.225.105.170]) by hub.freebsd.org (Postfix) with ESMTP id 1121B37BC06 for ; Wed, 12 Jul 2000 07:15:37 -0700 (PDT) (envelope-from rneswold@drmemory.fnal.gov) Received: (from rneswold@localhost) by drmemory.fnal.gov (8.9.3/8.9.3) id JAA02169; Wed, 12 Jul 2000 09:06:11 -0500 (CDT) (envelope-from rneswold) Date: Wed, 12 Jul 2000 09:06:11 -0500 From: Rich Neswold To: "David J. Kanter" Cc: ports@freebsd.org Subject: Re: Wmnet port doesn't display tunneling device Message-ID: <20000712090611.A2125@drmemory.fnal.gov> Reply-To: rneswold@enteract.com References: <20000711185241.A329@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000711185241.A329@localhost.localdomain>; from djkanter@northwestern.edu on Tue, Jul 11, 2000 at 06:52:41PM -0500 X-GnuPG-Fingerprint: FACD A985 1E15 FCEB BE76 1535 2F05 5DF1 143A 85D5 X-GnuPG-PubKey: ftp://ftp.enteract.com/users/rneswold/pub.key X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wasn't it 11-Jul-2000, at 06:52PM, when David J. Kanter said: > After upgrading from FreeBSD 3.5 -> 4.0, my wmnet no longer works > consistently or properly. It does not consistently display tun0, and the > device display name is off. > > In my kernel config I have pseudo-device tun, but wmnet -i tun0 will only > display ppp0. Cycling through sometimes eventually reveals a tun0, other > times no tun0 is available. > > I uninstalled, then reinstalled the port and it worked OK. But then I > logged out and logged back in and it did not work. > > Also, if you cycle through the devices with the mouse and get to one of > those longer devices, like faith, the "0" from faith0 remains in the LED > section when cycling through the devices again. When I ported the app (and rewrote the interface stuff), I was using 2.2.8. I know some things changed in 3.X -- although not enough to break the app. I'll look into the 4.0 internals to see if it has deviated further. I use wmnet all the time with no problems. But I haven't monitored the tunnel device in a while and my network card name is short enough, so I didn't catch the overrun. Thanks for the problem reports! -- Rich Neswold efax: 1.240.536.7092 web: www.enteract.com/~rneswold/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message