Date: Sun, 25 Mar 2001 17:00:10 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: Yonatan Bokovza <Yonatan@xpert.com> Cc: "'hackers@freebsd.org'" <hackers@freebsd.org> Subject: Re: nmap 2.54B22 Permission Denied error Message-ID: <Pine.NEB.3.96L.1010325165913.62604A-100000@fledge.watson.org> In-Reply-To: <EB513E68D3F5D41191CA00025558810171D4@mailserv.xpert.com>
next in thread | previous in thread | raw e-mail | index | archive | help
One potential source of Permission Denied on a network socket for the root user is the ipfw system. Do you have IP firewalling enabled, using either ipfw or ipfilter, and if so, could those rules potentially be denying the packets being generated? If you have logging/counters available for those rules, do they go up when you run nmap? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 25 Mar 2001, Yonatan Bokovza wrote: > When testing the new -sO feature, I got this: > > bash-2.04# nmap -sO 10.0.0.1 > Starting nmap V. 2.54BETA22 ( www.insecure.org/nmap/ ) > sendto in send_ip_raw: sendto(3, packet, 20, 0, 10.0.0.1, 16) => Permissi > on denied > Sleeping 15 seconds then retrying > sendto in send_ip_raw: sendto(3, packet, 20, 0, 10.0.0.1, 16) => Permissi > on denied > Sleeping 60 seconds then retrying > ^Ccaught SIGINT signal, cleaning up > > Note i'm root. > My sniffer shows outgoing and incoming packets as expected, i.e. > zero sized length packets of different protocols. > This is -stable of Mar-14. > Anyone else seeing this? > > Yonatan. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010325165913.62604A-100000>