From owner-freebsd-security Wed Feb 12 8: 3: 1 2003 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFBB937B406 for ; Wed, 12 Feb 2003 08:02:57 -0800 (PST) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85B1C43FB1 for ; Wed, 12 Feb 2003 08:02:55 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b146.otenet.gr [212.205.244.154]) by mailsrv.otenet.gr (8.12.6/8.12.6) with ESMTP id h1CG2q4A004227; Wed, 12 Feb 2003 18:02:53 +0200 (EET) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.7/8.12.7) with ESMTP id h1CG2pNQ003412; Wed, 12 Feb 2003 18:02:51 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.7/8.12.7/Submit) id h1CFtwqK003190; Wed, 12 Feb 2003 17:55:58 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 12 Feb 2003 17:55:58 +0200 From: Giorgos Keramidas To: Redmond Militante Cc: freebsd-security@FreeBSD.org Subject: Re: n00b ipf/ipnat questions Message-ID: <20030212155558.GB2237@gothmog.gr> References: <20030211002256.GA824@darkpossum> <20030211090154.R30313-100000@cactus.fi.uba.ar> <20030211141831.GB824@darkpossum> <1044990692.294.26.camel@ds9.sourcefire.com> <20030211190738.GB791@darkpossum> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030211190738.GB791@darkpossum> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2003-02-11 13:07, Redmond Militante wrote: > yeah > the reason i didn't think that portsentry would be causing this type > of behavioris that i'm also running it on a couple of standalone > workstations that i have firewalled with ipfilter, and when i nmap > these machines, it doesn't show a variety of ports being open due to > portsentry listening on them. That depends on what the default policy of the firewall is. If you use a ruleset that blocks all ports and allows only certain incoming packets, portsentry won't ever get a chance of seeing the blocked packets. This will not show anything to an nmap scan. If, on the other hand, you use a ruleset that allows everything through and only blocks certain ports or port-ranges, then portsentry will receive a lot more packets that before. This will show up as a huge list of open ports in an nmap scan. > i'm not sure why nmap would show these ports that portsentry's > listening on being open when behind a ipf/ipnat configuration... I'm not sure what your exact setup is (I have missed the beginning of this thread) so I can't answer this. - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message