On 2002-03-22 at 07:58 -0600, hanasaki wrote:
> traceroute to skmx01p1.americancentury.com (64.57.40.35) ...
> 1 10.61.96.1 (10.61.96.1) 10.190 ms 8.414 ms 7.733 ms
> 2 pos6-0.kscymoworn-rtr1.kc.rr.com (24.94.161.161) 8.446 ms 12.975
Meep!
10.something on the first hop? That's private address space. I _hope_
that's just the first hop's IP address.
If BSD-ish network-stack-wise, then it's probably worth doing
$ route -n get 64.57.40.35
[ note the "interface:" value ]
$ ifconfig if0 [ where "if0" is the interface. Eg, for me "xl0" ]
[ note the "inet" value ]
If the inet value there, your IP address also starts 10. then you're in
private address space (RFC 1918) and the remote side can't route back to
you. Hence you can't connect. If the web-browser is either using a
cache or a SOCKS proxy, then that would explain all of this.
If the IP address doesn't start 10., then .... how much do you know
about the network media local to you, and what MTU is being used? If
that _changes_ at the 10.61.96.1 then you're going to have network
problems to a lot of sites, since path MTU discovery will be broken.
--
Legislation needs a better reason than that lawyers like it,
and that America does it. -- Lawrence Lessig
