Re: [GNUnet-developers] Topology

[Blake Matheny]

Unfortunatly a bunch of traceroutes doesn't neccesarily help you
know the topology of a system. Take this sample traceroute from
my machine on a cable modem:
traceroute to google.com (216.239.35.100), 30 hops max, 40 byte packets
 1  10.10.10.254  0.511 ms  0.311 ms  0.336 ms
 2  10.9.88.1  11.436 ms  103.969 ms  12.519 ms
 3  12.220.5.33  39.701 ms  14.783 ms  103.660 ms
 4  12.220.1.70  124.129 ms 12.220.1.74  87.233 ms  65.619 ms
 5  12.220.0.18  27.632 ms  82.583 ms  28.329 ms
 6  12.123.5.78  29.869 ms  103.654 ms
What does that really tell me? From an outsider that doesn't tell
me anything. I know that 10.10.10.254 is my firewalls internal IP
address, and that 10.9.88.1 is my cable providers cisco router,
but there is no way that you could know this. All of the
methods I have found on doing intelligent topology discovery are
generally more invasive then most administrators would like, and
almost certainly give more information then GNUnet would like.
Anyonw have any other ideas? GNUnet knowing the network topology
would have several excellent advantages (speed, qos, etc).

-Blake

Whatchu talkin' 'bout, Willis?
> --
> This would require the network to know the topology in the first place. Code 
> to do that discovery would be great for GNUnet, too.
> --
> 
> this sounds a lot like a bunch of traceroutes to me, with the results being 
> cached.  unfortunatelly, my skills aren't anywhere near working with this 
> stuff yet.
> 
> --nathan
> 
> -- 
> 
> _______________________________________________
> Sign-up for your own FREE Personalized E-mail at Email.com
> http://www.email.com/?sr=signup
> 
> 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnunet-developers

-- 
Blake Matheny
address@hidden
PGP-Key http://www.dbaseiv.net/purdue.key