From owner-freebsd-questions@FreeBSD.ORG Wed Mar 22 09:59:00 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0B4316A400 for ; Wed, 22 Mar 2006 09:59:00 +0000 (UTC) (envelope-from norgaard@locolomo.org) Received: from strange.daemonsecurity.com (59.Red-81-33-11.staticIP.rima-tde.net [81.33.11.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21D9143D53 for ; Wed, 22 Mar 2006 09:59:00 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [172.24.8.84] (generic.atosorigin.es [212.170.156.200]) by strange.daemonsecurity.com (Postfix) with ESMTP id 1E15A2E041; Wed, 22 Mar 2006 10:59:05 +0100 (CET) Message-ID: <44211FE0.5000908@locolomo.org> Date: Wed, 22 Mar 2006 10:58:56 +0100 From: Erik Norgaard User-Agent: Thunderbird 1.5 (X11/20060118) MIME-Version: 1.0 To: Miguel References: <000d01c64d1d$95d2ac40$dc96eed5@ihlasnetym> <4420585F.1000006@123.com.sv> In-Reply-To: <4420585F.1000006@123.com.sv> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Halid Faith , freebsd-questions@freebsd.org Subject: Re: What does udp port 514 use? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2006 09:59:00 -0000 Miguel wrote: > Halid Faith wrote: > >> 2 - When I type netstat -na I see that udp port 514 is open as below >> udp4 0 0 *.514 *.* >> udp6 0 0 *.514 *.* >> >> Should I close this port ? then How can I close this port? >> > that is the syslog port for remote hosts' events , you can disable it > adding this to your rc.conf > > syslog_flags="-ss" The default setting is "-s" which means that syslog will not log events from foreign hosts. -ss means it wont listen at all on that port. There are few reasons to have syslog listening on that port: There might be some services running on you host (not that I know any) that try to write to the loopback interface rather than a UNIX socket. In that case you can force syslog only to bind to the loopback interface adding "-b localhost". Also, you should have your local firewall block incoming traffic. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9