Date: 10 Nov 1999 03:54:04 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: freebsd-questions@freebsd.org Subject: Re: Port 137 hitting my server Message-ID: <86u2mv862r.fsf@localhost.hell.gr> In-Reply-To: Peter Jeremy's message of "Wed, 10 Nov 1999 10:50:28 %2B1100" References: <86emdz68a0.fsf@localhost.hell.gr> <Pine.SOL.4.10.9911091512360.25266-100000@icg> <99Nov10.104437est.40326@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> 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, <keramida@ceid.upatras.gr> "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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86u2mv862r.fsf>