From owner-freebsd-hackers  Thu Nov 16 22:29:36 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA05139
          for hackers-outgoing; Thu, 16 Nov 1995 22:29:36 -0800
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA05110
          for <hackers@freebsd.org>; Thu, 16 Nov 1995 22:29:19 -0800
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id AAA02171 for hackers@freebsd.org; Fri, 17 Nov 1995 00:28:47 -0600
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199511170628.AAA02171@brasil.moneng.mei.com>
Subject: Evil constants in iijppp
To: hackers@freebsd.org
Date: Fri, 17 Nov 1995 00:28:47 -0600 (CST)
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-hackers@freebsd.org
Precedence: bulk

Spent a bit of time tonight trying to figure out why iijppp dies with > 4
connections active.  It appears that there is a hard coded "32" in the
interface scan routine at the end of "route.c", limiting the number of
interfaces iijppp is able to deal with (I had 4 ethers, 8 SLIP, 8 PPP, a few
misc, and 20 tunnels, or something like that, and the tunnels came at the
end).

I bumped the number to 1024 and all was sort of better.  Constants are evil
but if you have to use them, pick them large enough that nobody's likely to
notice anytime soon.  I don't see a readily apparent call that will return
the number of interfaces configured in the system, alas...

There is also some logic that needs to be reworked in the code that scans
the "tun" devices in /dev because right now it looks like it only deals with
numbers 0-9...  I didn't look into this very far, but it is on my list of
things to do.

Thanks,

... JG