From owner-freebsd-questions Fri Oct 2 02:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24356 for freebsd-questions-outgoing; Fri, 2 Oct 1998 02:44:27 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from abc.xyz.net (froggy.anchorage.ptialaska.net [208.151.119.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24350 for ; Fri, 2 Oct 1998 02:44:24 -0700 (PDT) (envelope-from groggy@iname.com) From: groggy@iname.com Received: from localhost (localhost [127.0.0.1]) by abc.xyz.net (8.8.8/8.8.8) with SMTP id BAA00925 for ; Fri, 2 Oct 1998 01:44:03 -0800 (AKDT) (envelope-from groggy@iname.com) Date: Fri, 2 Oct 1998 01:44:03 -0800 (AKDT) X-Sender: abc@abc.xyz.net To: freebsd-questions Subject: tunX = RUNNING, NOT! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm ending up with useless tunX (ppp) devices on a dialup server. they disappear if i reboot the machine, but otherwise, i can't get rid of bogus tunX: flags=8050 mtu 1500 lines in my ifconfig -a output. they should say: tunX: flags=8010 mtu 1500 what causes this? and what can i do about it? it's causing me to run out of available tunX devices. 2.2.7 running ppp -alias. i have a feeling it's from bad connects/disconnects ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message