Re: [OT] 3dfx.com. nvidia.com unreachable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Wed, May 23, 2001 at 12:03:47PM +0200, Justin Schoeman wrote:

> > - 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  * *

> Notice the last address: 10.0.0.2 - this isn't blocking, just hopelessly
> messed up routing tables (10.0.0.0 network is private, you may never see
> one of those adresses outside of you local network). Once you hit a
> 10.0.0.0 network outside of a local network, all bets are off...

	Actually, no.  This is not true.  Private addresses do show up
on traceroutes quite often.  It indicates a link in the route which is
using private addresses for internal routing.  You can't address it
directly but when it returns an error (TTL expired) it indicates the
address at which the failure occured.  That failure just happen to be
at one of those private addresses.  You should never see one of those
private addresses routed to or addressed to outside of your local
address and boarder gateways SHOULD filter out anything that has a
source address of a private address space, but, baring "policy routing",
stock routing does not take the source address into consideration in
the routing tables.  Lack of filtering?  Maybe...  Debatable.
Hopelessly messed up routing tables?  Not.

> -justin

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@xxxxxxxxxxxx
  (The Mad Wizard)      |  (678) 463-0932   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux