From owner-freebsd-isp Wed Feb 19 08:51:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA01751 for isp-outgoing; Wed, 19 Feb 1997 08:51:43 -0800 (PST) Received: from irbs.irbs.com (jc@irbs.irbs.com [199.182.75.129]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA01742 for ; Wed, 19 Feb 1997 08:51:39 -0800 (PST) Received: (from jc@localhost) by irbs.irbs.com (8.8.5/8.8.5) id LAA12101; Wed, 19 Feb 1997 11:51:17 -0500 (EST) Message-ID: <19970219115117.KS43971@irbs.com> Date: Wed, 19 Feb 1997 11:51:17 -0500 From: jc@irbs.com (John Capo) To: rbickers@intercenter.net (Ron Bickers) Cc: isp@FreeBSD.ORG Subject: Re: ypbind and many interface aliases References: X-Mailer: Mutt 0.60 Mime-Version: 1.0 X-Organization: IRBS Engineering, (954) 792-9551 In-Reply-To: ; from Ron Bickers on Feb 19, 1997 10:59:35 -0500 Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoting Ron Bickers (rbickers@intercenter.net): > > I'm running FreeBSD 2.1.6 + those patches that are suppose to show up as > 2.1.7 someday. > > ypbind will not bind with more than about 30 interface aliases (as in > 'ifconfig x.x.x.x alias' for web hosting). The portmapper forks like mad > until 'Cannot fork' messages show up in the log and until I kill ypbind. > Anyone else using yp and many interfaces without this problem? Or if you > have this problem, what's the fix? > The best solution is to not use aliases on a broadcast interface if you are running YP. Alias a subnet to lo0 instead and announce a route to the aliased net. Quite a while back I filed a PR with a hack to getbroadcastnets() that gets around the problem. I can dig it up if you want it. John Capo