From owner-freebsd-questions Wed Nov 10 8:28:39 1999 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 51B10153EC for ; Wed, 10 Nov 1999 08:28:29 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 11laR4-000NGW-00; Wed, 10 Nov 1999 16:17:26 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 11laR4-0000t5-00; Wed, 10 Nov 1999 16:17:26 +0000 Date: Wed, 10 Nov 1999 16:17:26 +0000 From: Ben Smithurst To: Giorgos Keramidas Cc: freebsd-questions@freebsd.org Subject: Re: Port 137 hitting my server Message-ID: <19991110161725.A3387@strontium.scientia.demon.co.uk> References: <86emdz68a0.fsf@localhost.hell.gr> <99Nov10.104437est.40326@border.alcanet.com.au> <86u2mv862r.fsf@localhost.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86u2mv862r.fsf@localhost.hell.gr> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Giorgos Keramidas wrote: > 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. You don't even need to recompile the kernel, ipfw works fine as a module (in my case at least, I'm not sure how you use the various IPFIREWALL_* options when ipfw is a kld). -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message