From owner-freebsd-security Tue Nov 9 15:27:33 1999 Delivered-To: freebsd-security@freebsd.org Received: from icg.interactivate.com (icg.interactivate.com [207.110.42.216]) by hub.freebsd.org (Postfix) with ESMTP id DC23114E1A for ; Tue, 9 Nov 1999 15:27:31 -0800 (PST) (envelope-from larry@interactivate.com) Received: from localhost (larry@localhost) by icg.interactivate.com (8.9.3/8.9.3) with ESMTP id PAA25279; Tue, 9 Nov 1999 15:13:17 -0800 (PST) Date: Tue, 9 Nov 1999 15:13:17 -0800 (PST) From: Larry Sica X-Sender: larry@icg To: Giorgos Keramidas Cc: freebsd-security@FreeBSD.ORG Subject: Re: Port 137 hitting my server In-Reply-To: <86emdz68a0.fsf@localhost.hell.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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) On 9 Nov 1999, Giorgos Keramidas wrote: > Peter Jeremy writes: > > > Unless you're feeling particularly ornery, in which case you > > could write a daemon which responded with various ICMP messages > > (returning a network redirect to 127.0.0.1 should quieten the > > offending machine :-). > > That is assuming that Windows machines will respect a net-redirect, > which having no such machines close to me right now I can not verify. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message