From owner-freebsd-isp Tue Oct 1 18:50:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA19926 for isp-outgoing; Tue, 1 Oct 1996 18:50:35 -0700 (PDT) Received: from itchy.mosquito.com (itchy.mosquito.com [206.205.132.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA19920 for ; Tue, 1 Oct 1996 18:50:33 -0700 (PDT) Received: (from boot@localhost) by itchy.mosquito.com (8.7.5/8.6.12) id VAA01131; Tue, 1 Oct 1996 21:50:24 -0400 (EDT) From: Bruce Bauman Message-Id: <199610020150.VAA01131@itchy.mosquito.com> Subject: out of sockets? To: freebsd-isp@freebsd.org Date: Tue, 1 Oct 1996 21:50:23 -0400 (EDT) Cc: portmaster-users@livingston.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We're a small ISP using Livingston portmasters and running radius on a single FreeBSD 2.1.5 box (along with e-mail, web server, and most other services). We recently started having customers complain that they were getting "Host is currently unavailable" messages when they tried to connect to our Portmasters. I'm assuming we've exhausted some networking resource. We've supped -stable, built a new kernel, and rebooted, but we're not sure whether the problem still exists. Is there any particular options in the kernel that should be tweaked? Any suggestions on where to look? -- Bruce