From owner-freebsd-questions Tue Nov 9 15:50:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B335215136 for ; Tue, 9 Nov 1999 15:50:37 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40326>; Wed, 10 Nov 1999 10:44:37 +1100 Content-return: prohibited Date: Wed, 10 Nov 1999 10:50:28 +1100 From: Peter Jeremy Subject: Re: Port 137 hitting my server In-reply-to: To: Larry Sica Cc: freebsd-questions@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Nov10.104437est.40326@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <86emdz68a0.fsf@localhost.hell.gr> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Nov-10 10:13:17 +1100, Larry Sica wrote: >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) This is something for -questions. You are getting messages like: Connection attempt to UDP 192.168.123.123:137 from 192.168.234.3:137 because you have the sysctl net.inet.udp.log_in_vain (and probably net.inet.tcp.log_in_vain) set to 1. These are controlled by the rc.conf parameter log_in_vain, (which defaults to "NO" ie off). You can remove all the `Connection attempt' messages by removing the line 'log_in_vain="YES"' from your /etc/rc.conf. 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). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message