From owner-freebsd-security  Mon Nov  8 20:40:30 1999
Delivered-To: freebsd-security@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 88B5D1507E
	for <security@FreeBSD.ORG>; Mon,  8 Nov 1999 20:40:26 -0800 (PST)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40371>; Tue, 9 Nov 1999 15:33:30 +1100
Content-return: prohibited
Date: Tue, 9 Nov 1999 15:39:18 +1100
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: Port 137 hitting my server
In-reply-to: <ML-3.4.942120308.1653.patl@asimov>
To: patl@phoenix.volant.org
Cc: security@FreeBSD.ORG
Reply-To: peter.jeremy@alcatel.com.au
Message-Id: <99Nov9.153330est.40371@border.alcanet.com.au>
MIME-version: 1.0
X-Mailer: Mutt 1.0pre3i
Content-type: text/plain; charset=us-ascii
References: <19991109031211.EF813152E9@hub.freebsd.org>
 <ML-3.4.942120308.1653.patl@asimov>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On 1999-Nov-09 15:05:08 +1100, patl@phoenix.volant.org wrote:
>I looked into it a while back; and the consensus was that they are
>harmless and not even worth logging.

Unless you're feeling particularly ornery, in which case you
could write a daemon which responded with various ICMP messages
(returning a network redirect to 127.0.0.1 should quieten the
offending machine :-).

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message