Nmap Development mailing list archives
Re: nmap Mac OS X Firewire Issue
From: David Fifield <david () bamsoftware com>
Date: Thu, 16 Jul 2009 09:00:38 -0600
On Wed, Jul 15, 2009 at 10:54:34AM -0400, Julian Berdych wrote:
The latest version of nmap (4.90RC1) still craps out on any Mac OS X system that has FireWire ports (see the nmap output below). This is pretty serious, as all Macs these days have FireWire ports, even the low-end MacBooks.
Thanks for reporting this. I was not previously aware of it. It had never happened to me on a Mac with FireWire ports. However, I was able to reproduce the problem by assigning an IP address to the fw0 interface. I couldn't do this through System Preferences, I had to use ifconfig. This doesn't happen to me on a Mac with FireWire ports. Does it only happen when something is plugged into one of the ports? I tried enabling the interface through System Preferences but it says "No network capable FireWire devices are connected." We'll look into this. For a short-term workaround, just remove the IP address associated with the FireWire interfaces. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- nmap Mac OS X Firewire Issue Julian Berdych (Jul 15)
- Re: nmap Mac OS X Firewire Issue David Fifield (Jul 16)
- Re: nmap Mac OS X Firewire Issue David Fifield (Jul 21)
- Re: nmap Mac OS X Firewire Issue David Fifield (Jul 16)