Page 1 of 1
| Subversive | The Newbie's Guide to Detecting the NSA
Posted: Thu Jun 29, 2006 10:36 am
by JaNell
(I labeled it for Homefatherland SSecurity)
The Newbie's Guide to Detecting the NSA
One way to tell if you're being watched on the web by Big Bubba.
Posted: Thu Jun 29, 2006 7:34 pm
by necrosynthesis
ha. It seems knology has circumvented the described procedure. It killed my connection altogether and I had to have it reset on knology's end. They were very curious about what I was doing. weird.
Posted: Thu Jun 29, 2006 8:09 pm
by iblis
necrosynthesis wrote:ha. It seems knology has circumvented the described procedure. It killed my connection altogether and I had to have it reset on knology's end. They were very curious about what I was doing. weird.
what, doing a traceroute?
Posted: Thu Jun 29, 2006 8:52 pm
by necrosynthesis
yes. I'm not sure what happened, as it's not my area of expertise, but they said they had to 'reset it on their end' whatever that means. Maybe I did something wrong.

Posted: Thu Jun 29, 2006 11:04 pm
by iblis
necrosynthesis wrote:yes. I'm not sure what happened, as it's not my area of expertise, but they said they had to 'reset it on their end' whatever that means. Maybe I did something wrong.

i've never heard of a trace route messing up a router - unless the thing was like 20 years old... or deliberately programmed to go ape from a traceroute - which i'm doubting, since people do traceroutes all the time.
i think it's more likely that they fucked up something - or something went belly up without their intervention - and they wanted a scapegoat.
Posted: Thu Jun 29, 2006 11:31 pm
by Dark Elf
Dont quite follow it all, but it creeps me out! Nice, new Avitar Ibliss!
Posted: Thu Jun 29, 2006 11:32 pm
by Dark Elf
.... and im too parinoid to try the described task above on the work computer...
Posted: Fri Jun 30, 2006 1:07 pm
by elasticwings
I'm sure everybody crosses an ATT router at some point. See, I do.
Code: Select all
wayne@sailorvenus:~$ traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 64.233.167.99
traceroute to google.com (64.233.167.99), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.851 ms 1.334 ms 1.293 ms
2 73.31.72.1 (73.31.72.1) 12.013 ms 7.863 ms 8.961 ms
3 s01b1.oakridge.tn.knox.comcast.net (68.86.194.225) 10.632 ms 8.114 ms 10. 895 ms
4 s01j1.knoxville.tn.knox.comcast.net (68.86.194.246) 10.182 ms 10.388 ms 1 6.311 ms
5 68.47.160.62 (68.47.160.62) 9.428 ms 10.492 ms 9.194 ms
6 12.124.64.61 (12.124.64.61) 34.006 ms 16.573 ms 19.388 ms
7 tbr1-p013701.attga.ip.att.net (12.123.20.170) 19.916 ms 16.178 ms 17.855 ms
8 ggr2-ge00.attga.ip.att.net (12.123.20.201) 17.425 ms 16.304 ms 16.343 ms
9 192.205.33.90 (192.205.33.90) 19.958 ms 18.222 ms 16.109 ms
10 atl-core-01.inet.qwest.net (205.171.21.105) 16.747 ms 16.563 ms 20.306 ms
11 cer-core-01.inet.qwest.net (67.14.8.14) 61.625 ms 49.354 ms 50.948 ms
12 chx-edge-01.inet.qwest.net (205.171.139.162) 50.252 ms 50.390 ms 49.618 m s
13 65.112.69.202 (65.112.69.202) 48.622 ms 47.908 ms 49.444 ms
14 216.239.46.1 (216.239.46.1) 52.755 ms 59.714 ms 48.377 ms
15 66.249.95.121 (66.249.95.121) 48.908 ms 48.916 ms 55.031 ms
16 64.233.175.34 (64.233.175.34) 54.767 ms 51.999 ms 50.417 ms
17 72.14.232.74 (72.14.232.74) 58.302 ms 61.912 ms 64.233.175.42 (64.233.175. 42) 50.562 ms
18 64.233.167.99 (64.233.167.99) 53.124 ms 53.923 ms 52.546 ms
wayne@sailorvenus:~$
And yes, my computer is named SailorVenus.
Posted: Fri Jun 30, 2006 1:33 pm
by karmakaze
necrosynthesis wrote:yes. I'm not sure what happened, as it's not my area of expertise, but they said they had to 'reset it on their end' whatever that means. Maybe I did something wrong.

try it again and see what happens. your not doing anything wrong.
Posted: Fri Jun 30, 2006 6:06 pm
by necrosynthesis
now i'm getting tracert not recognized as a command. I'll get somebody over here that knows what's up.
Posted: Fri Jun 30, 2006 10:07 pm
by iblis
necrosynthesis wrote:now i'm getting tracert not recognized as a command. I'll get somebody over here that knows what's up.
that
is odd.
you should get something like this:
C:\Documents and Settings\youbitchesareallgoingtodie>tracert
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.
ah well.