From owner-freebsd-security Tue Nov 9 15:40: 4 1999 Delivered-To: freebsd-security@freebsd.org Received: from athserv.otenet.gr (athserv.otenet.gr [195.170.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 474BA14CF0 for ; Tue, 9 Nov 1999 15:39:59 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (patr530-a029.otenet.gr [195.167.115.29]) by athserv.otenet.gr (8.9.3/8.9.3) with SMTP id BAA13423 for ; Wed, 10 Nov 1999 01:39:57 +0200 (EET) Received: (qmail 2728 invoked by uid 1001); 9 Nov 1999 23:41:58 -0000 To: freebsd-security@freebsd.org Subject: Re: Port 137 hitting my server References: From: Giorgos Keramidas Date: 10 Nov 1999 01:41:58 +0200 In-Reply-To: Larry Sica's message of "Tue, 9 Nov 1999 15:13:17 -0800 (PST)" Message-ID: <86u2mvgrll.fsf@localhost.hell.gr> Lines: 17 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Larry Sica writes: > actually the only thing i'd want to do is get rid of the annoying log > messages. How could i tell syslog not to log that particular things (this > is veering offt opic now i think) I am assuming that you're using ipfw here, and that you have a rule looking something like: 0600 deny log from any to any 137 via if0 or close to this. Remove the 'log' keyword and you're done with logging of these packets. -- Giorgos Keramidas, "What we have to learn to do, we learn by doing." [Aristotle] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message