Post by roberson on Mar 30, 2018 5:43:56 GMT
Mar 30, 2018 5:32:14 GMT @mcgruffthecrimedog said:
That post was meant to describe LE's limitations when it comes to tracing ip addresses. Even if you were to send LE an ip address that you deemed suspicious, LE would need enough facts to cause a judge to believe that there is probable cause that the ip address is connected to crime, in order to get a warrant they could serve on the ISP. You can resolve an ip address down to a really general geographical area and to an ISP without a warrant (anyone can do this), but not much more.Tracert isn't really used for "tracing" the geographical location of an ip address -- the "tracing" that is done is more for technical diagnostic issues. Tracert just maps the connection going from your ip address to the ip address you're querying; it doesn't have anything to do with geography. If you did tracert on just a regular person's ip address (not a server), the first hop would likely be your router, then it would hop through some other servers associated with your ISP, then it would hop through some servers associated with the other person's ISP, and then it would just time out when it arrived at the ip address you inputed. Really no useful information would be gleaned from doing a tracert.
And Wireshark is used for monitoring packets as they cross networks, not for tracing ip addresses. That's the software that is used to "sniff" and monitor wireless traffic. It's sometimes used by the bad guys to steal info on unsecured wireless networks.
And the software I had back in the day WAS much like tracert. Yes, tracert is used for diagnostics. Every tier 1 Windows tech knows that much. So is Ping and the linux and Mac equivalents. But tracert does have hops, which are essentially infrastructure locations, which of course have physical, real-world locations. Anyone can run a tracert and see this. It's not magic. It's going down the pipe to the destination. The software I had would correlate these locations to the real world placements, all against a map. So it was very much like tracert, simply more sophisticated and of course could not resolve down to individual homes.
As for WireShark, it's a packet sniffer, true, which is sort of the point. Basically the idea is to sniff packets as they come in, looking/filtering for particular information. WireShark is also a suite of TCP/IP tools. I imagine, given it's complexity, it can probably do what the website I listed can do. I can't see why not, although I don't have use or experience with it. Regardless, that's exactly why I listed the website: to illustrate the ability of the software I once owned and might expect WireShark to provide natively.
In any case, the entire idea is a nonstarter. Legally, technically, practically. Ethically.
EDIT: so here's some information on using ICMP packets to tracert using WireShark:
en.wikiversity.org/wiki/Wireshark/ICMP_Trace
Not seeing that it can do what my old software did, but there was nothing special about that or that website I posted.
Hell the software I had was twenty years ago! And now you can do it HTML, Javscript and some web framework.
Here's another graphical tracert tool:
www.monitis.com/traceroute/
Free Network Trace Test
Are you having network problems? Troubleshoot network related issues with Monitis Visual Traceroute!
Monitis visual traceroute is a free diagnostic tool that displays the path the Internet packets take across IP networks to reach a specific destination on a network. Enter the domain name, or IP address, of the web server you want to test and the tool will perform a trace route from different cities and countries around the world.
You will get a report identifying the approximate geophysical location of each hop and visualizing the route on Google maps. The easy to read report will help you detect bottlenecks, quickly track down and then solve problems.
Are you having network problems? Troubleshoot network related issues with Monitis Visual Traceroute!
Monitis visual traceroute is a free diagnostic tool that displays the path the Internet packets take across IP networks to reach a specific destination on a network. Enter the domain name, or IP address, of the web server you want to test and the tool will perform a trace route from different cities and countries around the world.
You will get a report identifying the approximate geophysical location of each hop and visualizing the route on Google maps. The easy to read report will help you detect bottlenecks, quickly track down and then solve problems.