Nmap Development mailing list archives
Re: Mac OS X: failed to determine route
From: Dion Stempfley <dion.stempfley () gmail com>
Date: Tue, 27 Jan 2009 06:28:16 -0500
On Jan 16, 2009, at 3:43 PM, Corey Chandler wrote:
Dion Stempfley wrote:I did a search but didn't find anything that exactly relates to my problem. Please forgive if this has been addressed in the past.I am testing nmap 4.76 on my Macbook Air and I noticed an interesting problem. When I initially scan using root, I get an error. If I run the same command as a user and then try again as root it succeeds. Any thoughts on the inconsistency?Strange, I'm running 10.5.6 and see no problems. Is there anything non-standard about your system (a firewall running, some security settings enabled)?-- Corey Chandler / KB1JWQ Living Legend / Systems Exorcist Today's Excuse: Program load too heavy for processor to lift
Thanks for the reply,I'm running 10.5.6 as well. The only thing I can think of is that I had installed Cisco VPN at one point, then removed it using the removal script. But I don't necessarily trust that Cisco subscribes to the "do no harm" method of product installation/uninstallation :) What is the best way to look at modules that might be loaded that affect the network interfaces?
Thanks, /Dion _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Mac OS X: failed to determine route Dion Stempfley (Jan 16)
- Re: Mac OS X: failed to determine route Corey Chandler (Jan 16)
- Re: Mac OS X: failed to determine route Dion Stempfley (Jan 27)
- Message not available
- Re: Mac OS X: failed to determine route Corey Chandler (Jan 27)
- Re: Mac OS X: failed to determine route Corey Chandler (Jan 16)
- Re: Mac OS X: failed to determine route David Fifield (Jan 16)