From owner-freebsd-stable Wed Jul 9 13:29:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06222 for stable-outgoing; Wed, 9 Jul 1997 13:29:58 -0700 (PDT) Received: from tarkin.smlab.com (tarkin.smlab.com [208.132.36.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06214 for ; Wed, 9 Jul 1997 13:29:53 -0700 (PDT) Received: from r2d2.smlab.com (mike@r2d2.smlab.com [192.168.2.7]) by tarkin.smlab.com (8.8.5/8.7.3) with SMTP id QAA10401; Wed, 9 Jul 1997 16:34:37 -0400 (EDT) Received: from localhost (mike@localhost) by r2d2.smlab.com (8.6.11/8.6.11) with SMTP id QAA00373; Wed, 9 Jul 1997 16:28:42 -0400 Date: Wed, 9 Jul 1997 16:28:41 -0400 (EDT) From: Mike Nowlin To: Tom cc: stable@FreeBSD.ORG Subject: Re: limit socket connections on 2.1.7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Jul 1997, Tom wrote: > > On Wed, 9 Jul 1997, Mike Nowlin wrote: > > > I'd like to limit the number of incoming TCP connections to a range of > > port numbers (8000-8999). ("Limit port 8000 to 4 connections, 8001 to 10 > > connections, and 8002 to 13 connections" type of thing...) > > This type of thing is normally done at the application level, not in the > kernel. Whatever application you are using, should not open more > connections than you want. > Yea -- normally I'd do it that way... HOWEVER...... This is being used for a "for sale by connection" service, where the customers have access to their source code... I sell them a TCP port, they run their software on it....... I could require they put a certain block of code in their programs that restrict the number of connections, but that would be a bit difficult to monitor/enforce......... Mike