From owner-freebsd-ports Wed Jul 12 9:57:28 2000 Delivered-To: freebsd-ports@freebsd.org Received: from wop21.wop.wtb.tue.nl (wop21.wop.wtb.tue.nl [131.155.56.216]) by hub.freebsd.org (Postfix) with ESMTP id 0BB5F37B5EB for ; Wed, 12 Jul 2000 09:57:25 -0700 (PDT) (envelope-from karelj@wop21.wop.wtb.tue.nl) Received: (from karelj@localhost) by wop21.wop.wtb.tue.nl (8.9.3/8.9.3) id SAA12148; Wed, 12 Jul 2000 18:57:21 +0200 (CEST) (envelope-from karelj) Date: Wed, 12 Jul 2000 18:57:20 +0200 From: "Karel J. Bosschaart" To: Rich Neswold Cc: "David J. Kanter" , ports@FreeBSD.ORG Subject: Re: Wmnet port doesn't display tunneling device Message-ID: <20000712185720.A12125@wop21.wop.wtb.tue.nl> Reply-To: K.J.Bosschaart@tue.nl References: <20000711185241.A329@localhost.localdomain> <20000712090611.A2125@drmemory.fnal.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000712090611.A2125@drmemory.fnal.gov>; from rneswold@enteract.com on Wed, Jul 12, 2000 at 09:06:11AM -0500 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 12, 2000 at 09:06:11AM -0500, Rich Neswold wrote: > 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. > I think the problem with tun0 is that in 4.0 the tun0 device is created dynamically when it is needed. Therefore it doesn't always show up in wmnet. Karel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message