I have, for some time, been able to ssh into my father's FreeBSD machine in 
the Road Runner network in Central New York.  Last night, I tried so that I 
could fix a problem for him and ssh timed out.  No problem I thought, his 
modem has a different IP than the one I have in my /etc/hosts file, but this 
turned to not be the case.

Well, after some digging, I did a traceroute to his IP address.  The packets 
went all over the place, from San Jose, to Colorado, back to San Jose, to 
Colorado then to Ohio, then to Denver, then to San Jose, then to Ohio, etc. 
(you get the idea).  Eventually, traceroute was just lost and confused and I 
hit ctrl-c.  Thinking the problem would work itself out, I decided to wait 
and try again tonight however, I'm having the same problem tonight.

Obviously, though, I can use my Internet connection (after all, the 
e-mail . . .), but why can't I get to his IP address.  For kicks and grins 
tonight, I logged onto my DSL modem and looked at it's routing table.  I 
found some interesting information.

First, my DSL modems IP is, however, the default route appears 
to be  Obviously, I've got to cross at least one network to get 
to this default route in the first place.  I'm assuming this is the default 
route because it appears in the routing table as such:

dest            netmask         gateway

Now, here's the output of traceroute (with name resolution turned off):

-> traceroute -n
traceroute to (, 64 hops max, 52 byte packets
 1  * * *
 2  40.303 ms *  39.421 ms

Why on earth would there be delays on the first hop when not using name 

Ok, now my machines setup: my DSL modem is the router (as you all knew).  It 
also acts as a DHCP server but my FreeBSD machine is setup as static IP.  The 
local, private, IP network is with the DSL modem as and my box is statically assigned

Any thoughts as what might be wrong on my end before I start bugging my ISP?

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to