1 Jan 2004 14:15
RE: Traces
Fernando Gont <fernando <at> gont.com.ar>
2004-01-01 13:15:44 GMT
2004-01-01 13:15:44 GMT
At 16:05 31/12/2003 -0800, Shawn Jackson wrote: > Okdokie. Let's say I am pinging anything.org and its 5 hops >away. Let's also say that through a status route change (a BGP peer goes >down, etc) I'm being router through a different backbone, now >anything.org is 8 hops away due to that change. Great it's 8 hops away. Note that you only need that packets take the same routes for some stable period of time. A BGP peer going down is the exception, not the rule. >you can't garner that information without, at least, a netblock. The ATM >core can be connected to thousands of networks, using that information >you can only have a meager guess at which backbone provider the attack >is coming from. As I said in my last e-mail, the more data you have, the more accurate your guess may be. (See my example bellow). > TTL is not like miles it can't be efficiently measured. Routers >can be hundreds of miles apart, or a few feet. I can reach the Easter >half of the US in less hops then it takes me to get to Mexico, does that >means its closer, nope. Could I take a look at a TTL and say what state >it's in, nope. And what does this have to do with our discussion???? You don't need to know where the attacker *physically* is. You just need to know where he is, but from a "networking" point of view. You need to detect which router he is attached to. > Can you give me an example of it in action? How would you use it(Continue reading)
RSS Feed