From owner-freebsd-hackers  Mon Jun  9 07:36:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA25124
          for hackers-outgoing; Mon, 9 Jun 1997 07:36:52 -0700 (PDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA25111
          for <freebsd-hackers@freefall.FreeBSD.org>; Mon, 9 Jun 1997 07:36:45 -0700 (PDT)
From: sthaug@nethelp.no
Received: (qmail 8011 invoked by uid 1001); 9 Jun 1997 14:36:33 +0000 (GMT)
To: bob@luke.pmr.com
Cc: freebsd-hackers@freefall.FreeBSD.org
Subject: Re: What's the magic to enable tcpblast?
In-Reply-To: Your message of "Mon, 9 Jun 1997 08:49:13 -0500"
References: <19970609084913.37927@luke.pmr.com>
X-Mailer: Mew version 1.05+ on Emacs 19.28.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Mon, 09 Jun 1997 16:36:32 +0200
Message-ID: <8009.865866992@verdi.nethelp.no>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I have noticed that I can no longer run tcpblast between my systems.
> I always get (to my systems with newer releases of FreeBSD):
> 
> tcpblast connect:: Connection refused
> 
> Is there some security restriction that I can loosen up on that
> will enable tcpblast to run?  BTW, to my old system (2.1-STABLE
> circa 1995) tcpblast still works.

Have you checked inetd.conf? On newer versions of FreeBSD, it says:

# "Small servers" -- used to be standard on, but we're more conservative
# about things due to Internet security concerns.  Only turn on what you
# need.
#
#daytime stream tcp     nowait  root    internal
#daytime dgram  udp     wait    root    internal

(etc. for time, echo, discard and chargen).

Steinar Haug, Nethelp consulting, sthaug@nethelp.no