From owner-freebsd-questions Tue Oct 20 09:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06540 for freebsd-questions-outgoing; Tue, 20 Oct 1998 09:46:03 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06485 for ; Tue, 20 Oct 1998 09:45:56 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA27244; Tue, 20 Oct 1998 09:45:21 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 20 Oct 1998 09:45:20 -0700 (PDT) From: Doug White To: Markus Holmberg cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslogd listening on udp 514 even after user '-s' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Oct 1998, Markus Holmberg wrote: > Hm.. It gives the same output for each time I check which ports there is > something listening on.. > > In what way do you mean someone is trying to abuse it? You mean someone is > sending UDP's to fill my syslogs up? I can't see how that is related to > this.. The problem was that I used the '-s' flag when starting syslogd up, > which should mean it should *not* be listening on the port.. But it > obviously does! (For more ppl than just me).. Try using netcat and spew some stuff at port 514 and watch what happens. I hate that too (it solves the problem and creates another of the same class) but it's not as bad as it could be. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message