From owner-freebsd-hackers  Sat Nov  9 21:22:30 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA15371
          for hackers-outgoing; Sat, 9 Nov 1996 21:22:30 -0800 (PST)
Received: from cheops.anu.edu.au (daemon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA15358
          for <hackers@FreeBSD.ORG>; Sat, 9 Nov 1996 21:22:24 -0800 (PST)
Message-Id: <199611100522.VAA15358@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA249209402; Sun, 10 Nov 1996 12:30:02 +1100
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: Inetd mod.. comments?
To: smpatel@umiacs.umd.edu (Sujal Patel)
Date: Sun, 10 Nov 1996 12:30:02 +1100 (EDT)
Cc: julian@whistle.com, hackers@FreeBSD.ORG
In-Reply-To: <Pine.OSF.3.91.961109160517.3417C-100000@mickey.umiacs.umd.edu> from "Sujal Patel" at Nov 9, 96 04:13:17 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Sujal Patel, sie said:
[...]
> 1 - Rate limit incoming TCP connections to a specified port.
> 2 - Rate limit ICMP/UDP traffic.

These two will come when the RSVP folk get things finalised.

> 3 - Limit the number of concurrent TCP connections to a port.
> 4 - Limit the number of concurrent TCP connections from a host/domain.

These are more properly enforced by whatever it is that is managing those
connections (ie inetd).

Darren