by bvonahsen » Fri Jun 30, 2006 1:13 pm
Here is the article with comments. I had the same results as the others. IP of 12.110.110.132 came up and after that nothing but timouts.<br><br><!--EZCODE QUOTE START--><blockquote><strong><em>Quote:</em></strong><hr>Remember when we discussed the secret room in San Francisco where ATT redirects internet traffic to NSA monitors? Wired has outlined a way to find out if your net activity is going there -- and thus, presumably, to Uncle.<br><br>The Wired site isn't accessible at this writing, but the story was republished in pertinent part by the Left Coaster. Basically, the technique is pretty simple.<br><br>If you're running Windows, go to Start/Run/cmd to get to the DOS prompt.<br><br>Then type tracert nsa.gov<br><br>Your computer will then try to find a path to the NSA (whose IP number is 12.110.110.204) in 30 easy steps. This process will take a little while.<br><br>The NSA's IP number probably won't show up in your traceroute -- but that's not the location you're really looking for. What you're looking for is that small room in San Francisco. Which means that the following string is key:<br><br>sffca.ip.att.net.<br><br>If those letters show up at any point in the trace route, you MAY have trouble. Here is what Wired writer Kevin Poulsen says: <br>If it's present immediately above or below a non-att.net entry, then -- by [AT&T whistleblower Mark] Klein's allegations -- your packets are being copied into room 641A, and from there, illegally, to the NSA.<br><br>Of course, if internet pioneer and former FCC advisor J. Scott Marcus (who held a Top Secret security clearance) is correct, and AT&T has installed these secret rooms all around the country, then any att.net entry in your route is a bad sign.<br>Naturally, I tried this trick. Naturally, the magic string -- sffca.ip.att.net -- showed up in my traceroute.<br><br>Two steps above it was an IP connected to my service provider. Sandwiched between this (quite legitimate) address and that dreaded room in San Francisco was this number: 144.232.9.206. I used this service to check out who owns that number; the trail led to a building in downtown L.A. An NSA outpost? Hell if I know.<br><br>Below the sffca number, the information was routed to another att.net location in Saint Louis, and from there to att.net in Washington, DC. From there, it went to a mysterious number in...Ohio.<br><br>At this point, my soi-disant computer savvy has reached its limit, and I'm not sure how to interpret the info. Where does paranoia end and legitimate concern begin? We need a True Geek to speak with authority on this matter.<br><br>Try this trick at home, kids. Tell me what you come up with. Perhaps someone who knows more about tracert can tell us whether those att.net addresses really do spell trouble.<br># posted by Joseph : 4:57 AM 5 comments <br><br><br><!--EZCODE BOLD START--><strong>Comments:</strong><!--EZCODE BOLD END--> <br>I tried it. On the 13th step, the IP of 12.110.110.132 came up. After that, which is suspiciously close to the NSA IP, every other step timed out.<br><br>Does this mean I'm on Nixon's enemy list? Or am I inflating my own self-importance?<br># posted by unirealist : 5:53 AM <br>Same thing happened here: 12.110.110.132 followed by time outs.<br># posted by Jeff : 6:59 AM <br>Just slightly different here. My 9th and 10th steps both had wswdc.ip.att.net as part of the address. My 12th was 12.110.110.131. After that, nothing but timeouts.<br># posted by Anonymous : 7:26 AM <br>lately in south carolina, numerous cities, if you report any phone or internet problems, Bellsouth now wants to COME TO YOUR HOME! Mind you, Bellsouth did not come to your home for any installations until recently. Also be aware that " sending a repairman" is the FIRST option now offered on ALL problems....<br>wierder than wierd and likewise the corporate response when they were asked if this new " service" was in any way connected to the NSA spying..<br>Be aware people.......<br># posted by Anonymous : 7:37 AM <br>A Quick google dig. Using an iplookup tool, the owner of 12.110.110.132 is LinguaLISTek. Here's a small company profile of them at <!--EZCODE AUTOLINK START--><a href="http://www.dnovus.com/seaport1.asp">www.dnovus.com/seaport1.asp</a><!--EZCODE AUTOLINK END--><br><br>"<br><br>LinguaLISTek is a Woman-Owned, Minority-Owned, and Veteran-Owned company, and is certified by the Small Business Administration as an 8(a), Small & Disadvantaged Business. LinguaLISTek has been in business since 1997, with their corporate office located in Columbia, Maryland, and a branch office in San Antonio, Texas. LinguaLISTek has additional personnel in auxiliary locations to include Georgia, North Carolina, and Pennsylvania.<br><br>Lingual Information System Technologies (LinguaLISTek), a leader in IT solutions and Language services, is dedicated to providing state-of-the-art language training, system/software development and life cycle support, networking, language and network security and IT business services and solutions to customers such as the National Security Agency, Defense Intelligence Agency, the United States Navy, US Army, and the US Air Force in various industries throughout the United States."<br><br>Through the iplookup, their ip range is directly connected to AT&T Worldnet Services.<br><br>Again, my tech savvy is limited as to what this may mean. But, grounds for paranoia and possibly some FOIA requests? I'd say it's likely.<hr></blockquote><!--EZCODE QUOTE END--> <p></p><i></i>