Date: Fri, 30 Jul 1999 10:20:53 -0400 (EDT) From: Seth <seth@freebie.dp.ny.frb.org> To: FreeBSD-gnats-submit@freebsd.org Subject: ports/12890: nmap seems to break under certain conditions in recent build Message-ID: <199907301420.KAA14361@freebie.dp.ny.frb.org>
next in thread | raw e-mail | index | archive | help
>Number: 12890
>Category: ports
>Synopsis: nmap seems to break under certain conditions in recent build
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Jul 30 07:30:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Seth
>Release: FreeBSD 3.2-STABLE i386
>Organization:
>Environment:
3.2-STABLE FreeBSD 3.2-STABLE #0: Tue Jul 27 14:48:55 EDT 1999
built 27 July 1999.
>Description:
After the latest build, nmap seems to have broken a bit. I've isolated it to
a case where the box has 2 NICs, and the first one is down AND has never been
configured.
xl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
(no inet line; ether deleted)
media: 100baseTX <full-duplex>
supported media: autoselect 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 10baseT/UTP
xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet w.x.96.162 netmask 0xffffc000 broadcast w.x.127.255
ether 00:c0:4f:xx:xx:xx
media: 100baseTX <full-duplex>
supported media: autoselect 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 10baseT/UTP
netstat -nr shows valid routes; in fact, I'm using the box remotely (off-net)
via xl1 to send this PR.
nmap -sS -O w.x.68.82 (same subnet as xl1) returns the following:
WARNING: Could not determine what interface to route packets through to
w.x.y.z, changing ping scantype to ICMP only
nmap with just -e xl1 returns
I cannot figure out what source address to use for device xl1, does it
even exist?
QUITTING!
nmap with both -e and -S seems to work.
Funny thing is: once you ifconfig xl0 (even with a bogus address), bring it
up, then bring it down, nmap works fine over xl1. It continues to work
even after ifconfig xl0 delete <bogus IP address>.
Thinking it might be something in bpffilter, I tried two other programs that
use it: ntop and tcpdump. No problems to report there.
>How-To-Repeat:
See above. Tried w/ nmap-2.12 and nmap 2.2-BETA4.
>Fix:
Workaround above: ifconfig xl0, down it, delete it.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907301420.KAA14361>