Eric Jorgensen wrote: > > Ben Bridgwater wrote: > > 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. True. Not that I think above.net's blocking is malicious - just an extraordinarily poor way of handling the issue (open mail servers). > > 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. Hmm.. are you suggesting a firewall on my box or at my ISP? I'm just running a Linux box here with a default (Mandrake) network setup and dialup connection. Different situation at work of course. > 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. Or maybe they should just hand out free graphics cards to everyone inconvenienced?:-) Just building a shiny new kernel here so I can try btaudio with the new bttv and i2c stack... Ben
