From owner-freebsd-stable Thu Jul 29 14:19:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32]) by hub.freebsd.org (Postfix) with ESMTP id 3520314CB5 for ; Thu, 29 Jul 1999 14:19:15 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by fed-ef1.frb.gov; id RAA22134; Thu, 29 Jul 1999 17:17:30 -0400 (EDT) Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2) id xma022066; Thu, 29 Jul 99 17:17:15 -0400 Date: Thu, 29 Jul 1999 17:17:09 -0400 (EDT) From: Seth Subject: Re: nmap 2.12/2.2b4 stops working after 7/27 build? In-reply-to: To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to follow up on my own post, but: bringing up xl0, configuring a bogus IP address on it, then downing it fixes the problem. So I have a workaround, but I'm still wondering what changed. My last build (before July 27th) was June 11. Things were fine until this recent build. SB On Thu, 29 Jul 1999, Seth wrote: > nmap used to work with -sS -O ... after 7/27 buildworld, it fails with > > WARNING: Could not determine what interface to route packets through to > w.x.y.z, changing ping scantype to ICMP only > > > -e doesn't work either: > > I cannot figure out what source address to use for device xl1, does it > even exist? > QUITTING! > > > xl1 is up and active; it's the primary interface for this box. Netmask > and default routes are ok. The host to be scanned is on the local subnet. > xl0 is down and unconfigured. > > xl0: flags=8802 mtu 1500 > xl1: flags=8843 mtu 1500 > > > Can anyone else reproduce this behavior? > > Thanks, > > SB > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message