From owner-freebsd-isp  Thu Mar  6 20:53:56 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA13562
          for isp-outgoing; Thu, 6 Mar 1997 20:53:56 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA13496
          for <freebsd-isp@FreeBSD.ORG>; Thu, 6 Mar 1997 20:53:44 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id QAA04715; Fri, 7 Mar 1997 16:10:22 +1100 (EST)
Date: Fri, 7 Mar 1997 16:10:21 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Charles Reese <reese@chem.duke.edu>
cc: freebsd-isp@FreeBSD.ORG
Subject: Re: HELP: tun problem
In-Reply-To: <1.5.4.32.19970307040031.0068c928@chem.duke.edu>
Message-ID: <Pine.BSF.3.91.970307155757.2758K-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Thu, 6 Mar 1997, Charles Reese wrote:

> Thanks to everyone who responed to my tun ifconfig message.  I must have
> some other problem as I still can't get more then 1 line to work at a time.
> Here is the message I get when I try to connect with a second line.

OK, so you have lots of tun devs in /dev/ and kernel.  Do you have full 
sources available?  Can you hack?  The ppp code opens the tun device in 
os.c, at around line 265.  One thing to note is that my code in os.c 
handles tun0-tun65535, not tun9, tuna, tunb, etc.  It will never find 
tun[a-z], but you should have no problems with tun1.

Danny