Home page logo

nmap-dev logo Nmap Development mailing list archives

Re: Zenmap Topology
From: Houcem HACHICHA <houcem.hachicha () gmail com>
Date: Tue, 15 Mar 2011 18:22:20 +0100

On Tue, Mar 15, 2011 at 4:08 AM, David Fifield <david () bamsoftware com>wrote:

On Mon, Mar 14, 2011 at 03:25:14PM -0700, David Fifield wrote:
On Sat, Mar 12, 2011 at 12:30:30PM +0100, Houcem HACHICHA wrote:
Hi there,

Have anyone noticed how when a *--traceroute <target>* hits like 10
then does not reach the target, *Zenmap* *Topology* prints that target
the first ring?
Any idea how to get that target printed in the 11th or 12th ring

Can you send me the XML output of your scan? I've not noticed what
you're describing.

Okay, I see now. I attached a screenshot from the file you sent me. The
target is getting put in the first ring (with a dashed line) because its
hop distance isn't known. In this respect it's appearing just like it
would with no traceroute.

It's hard to know what to do in this case. Putting it at the next ring
out (with a dashed line) seems like a good idea in this case, even if we
don't know the true distance. But if there were another host in the
scan, even farther away, then its position at that distance could be
misleading. But maybe that's okay.

To answer your question, there's no way to get it to appear where you
want it currently. This will require a change to the source code.

David Fifield

IMO when analyzing a network topology it's always useful to spot at which
level traceroute probes get blocked. So I think putting the target at the
next ring (with a dashed line of course) is the best way to represent the
traceroute findings.
I think it's ok if there were other hosts at that distance, after all that's
why we put a dashed line not a solid one.

Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]