On Sat, 29 Mar 2003, jason wrote:
This has been going on since version 3.0 of nmap for freebsd..
su-2.05b# uname -a
FreeBSD monsterjam.org 4.8-RC FreeBSD 4.8-RC #0: Mon Mar 10 16:54:44
su-2.05b# nmap -sU 10.1.1.10
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
sendto in send_udp_raw:
This has been going on since version 3.0 of nmap for freebsd..
su-2.05b# uname -a
FreeBSD monsterjam.org 4.8-RC FreeBSD 4.8-RC #0: Mon Mar 10 16:54:44
su-2.05b# nmap -sU 10.1.1.10
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
sendto in send_udp_raw: sendto(3, packet, 28, 0, 10.1.1.10, 16) =
yeah, I know the -sU is for UDP scans. Im using ipfw. Im 99.9% sure
my firewall rules didnt change from version to version of nmap, but damn,
youre right! scanning with my firewall disabled worked. Good catch. I
guess ill have to play with my ipfw rules now. Thanks.
Jason
On Sat, 29 Mar 2003,
On Sat, 29 Mar 2003, jason wrote:
yeah, I know the -sU is for UDP scans. Im using ipfw. Im 99.9% sure
my firewall rules didnt change from version to version of nmap, but damn,
youre right! scanning with my firewall disabled worked. Good catch. I
guess ill have to play with my ipfw rules