From owner-freebsd-questions Tue Nov 9 17:52:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from athserv.otenet.gr (athserv.otenet.gr [195.170.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E5E481517C for ; Tue, 9 Nov 1999 17:52:26 -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 DAA22179 for ; Wed, 10 Nov 1999 03:52:13 +0200 (EET) Received: (qmail 3511 invoked by uid 1001); 10 Nov 1999 01:54:05 -0000 To: freebsd-questions@freebsd.org Subject: Re: Port 137 hitting my server References: <86emdz68a0.fsf@localhost.hell.gr> <99Nov10.104437est.40326@border.alcanet.com.au> From: Giorgos Keramidas Date: 10 Nov 1999 03:54:04 +0200 In-Reply-To: Peter Jeremy's message of "Wed, 10 Nov 1999 10:50:28 +1100" Message-ID: <86u2mv862r.fsf@localhost.hell.gr> Lines: 21 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: [snip] > If you just wait to stop messages about port 137 (or other specific > ports), your only option is to have a daemon listening on this port > and silently dropping all traffic for it. (I don't believe a suitable > daemon comes with FreeBSD, but would be trivial to write). In fact FreeBSd does have a nice way of rejecting all these connection attempts to port 137, but not a daemon per se. If you don't find recompiling the kernel a tedious task to do, the firewall support of FreeBSD is quite suitable for this task. A simple set of rules like 0100 deny udp from any to any 137 via if0 0200 pass ip from any to any should be enough for this task. -- 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-questions" in the body of the message