Ben Bridgwater wrote: > > "Clifton T. Sharp Jr." wrote: > > > > Ben Bridgwater wrote: > > > "Clifton T. Sharp Jr." wrote: > > > > Ben Bridgwater wrote: > > > > > Today I still can't access 3dfx's domain from work, but also not > > > > > nvidia.com and macromedia.com.. what the latter two have in common is > > > > > that traceroute indicates my route to them is thru above.net which per a > > For you to imply that your inability to get through is a deliberate act on > > Abovenet's part without any facts to back that assertion up is disingenuous > > at best. > > Well, if you weren't so heavy handed about cutting people off from > chunks of the net then you wouldn't be setting yourself up for > suspicion. > > Consider this from my point of view: > > - I read on /. about above.net blocking macromedia.com, but supposedly > unblocking them > > - I can't access nvidia.com, do a traceroute and there's above.net > > - I remember the story, check macromedia.com and bingo - above.net and > no access > > - I come come and check from here, and minus above.net I can get to > macromedia > > - I check nvidia from home, and same as Eric: > > 4 1.ATM1-0.BDL-0.WINSTAR.NET (209.141.211.29) 159.533 ms 169.546 ms > 139.776 ms > 5 14.winstar.net (63.141.227.14) 159.470 ms 149.594 ms 149.793 ms > 6 sl-gw18-nyc-7-2.sprintlink.net (144.232.235.193) 149.495 ms > 169.645 ms 149.699 ms > 7 sl-bb21-nyc-4-0.sprintlink.net (144.232.13.162) 149.560 ms 169.531 > ms 149.692 ms > 8 sl-gw9-nyc-9-0.sprintlink.net (144.232.7.98) 159.512 ms 169.566 > ms 149.742 ms > 9 sl-abovenet-12-0-155M.sprintlink.net (144.232.173.22) 149.543 ms > 169.565 ms 149.733 ms > 10 core2-core3-oc48.lga1.above.net (208.184.233.217) 149.552 ms > 150.634 ms 148.605 ms > 11 iad1-lga1-oc192.iad1.above.net (208.184.233.65) 159.484 ms 149.579 > ms 149.738 ms > 12 core1-core5-oc48.iad1.above.net (208.185.0.145) 160.684 ms 169.557 > ms 169.771 ms > 13 sjc2-iad1-oc48.sjc2.above.net (216.200.127.26) 220.104 ms 228.836 > ms 239.724 ms > 14 core5-sjc2-oc48-2.sjc1.above.net (208.184.102.205) 239.550 ms > 229.527 ms 240.410 ms > 15 main1-core5-oc12.sjc1.above.net (208.185.175.250) 238.888 ms > 229.529 ms 239.743 ms > 16 209.249.170.20.nvidia.com (209.249.170.20) 249.612 ms 228.921 ms > 239.750 ms > 17 10.0.0.2 (10.0.0.2) 239.545 ms 229.588 ms 229.720 ms > 18 * * * > 19 * * > * > > Guess who's the prime suspect? Well, you should never assume malice where the situation can be adequately explained by incompetence. It's possible that your firewall is (correctly) configured not to allow RFC1918 addresses on the internet side, and is blocking you from reaching this 10.0.0.2 machine because it shouldn't be there. So maybe it's a matter of sillyheads at nvidia (or whoever does their hosting) letting their private address space leak. An act deserving of multiple noogies. - Eric
