Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!in1.uu.net!newsfeed.pitt.edu!news.pgh.net!w2xo.pgh.pa.us!durham
From: Jim Durham <durham@w2xo.pgh.pa.us>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Pinging myself
Date: Fri, 18 Aug 1995 15:08:18 -0400
Organization: Pittsburgh OnLine, Inc.
Lines: 45
Message-ID: <Pine.BSF.3.91.950818150043.222A-100000@w2xo.pgh.pa.us>
References: <808168572snz@beckley.demon.co.uk> <40n1jo$isa@bonnie.tcd-dresden.de>
<808515947snz@beckley.demon.co.uk> <CSTRUBLE.95Aug15165127@quirk.com>
NNTP-Posting-Host: w2xo.pgh.pa.us
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <CSTRUBLE.95Aug15165127@quirk.com>
On 15 Aug 1995, Craig Struble wrote:
> In article <808515947snz@beckley.demon.co.uk> Ian W Taylor <iwta@beckley.demon.co.uk> writes:
>
> > However even ping 158.152.59.213 doesn't start working
> > until the ppp link is up. I presume this is for a
> > request for the 'name' for that numeric IP addr.
>
> You might want to make sure there's a route in your routing table that
> has 158.152.59.213 routed directly to localhost. Even that might not work,
> but if you have a default route out to your ISP, and no route
> specifically for your own IP to localhost, then the PPP link will
> definitely have to be brought up so that your machine can figure out
> how to route the packet.
>
> I have found some random programs that don't like having a route from
> my own IP address to localhost, but those are very rare.
> See ya later,
> Craig
This is particularly annoying when using tcsh, which seems to do a DNS
lookup for some reason.
If iijppp "jams up", it takes about 2 minutes to get a log-in prompt
when using tcsh. I assume that it is doing a similar "local" lookup
to the lookup which causes the ping problem. I also tried putting
"/etc/hosts" before the "bind" line in the config file and it didn't
satisy it.
I will try the route to localhost trick.
Seems that this issue should have a more elegant fix than creating a
route to localhost.
One thing suggested to me was to put a fully qualified localhost
address in /etc/hosts, because most DNS servers apparently have
a 127.0.0.1 entry such as "localhost@domain" so that such requests
don't fail and hang things up even further. It still seems silly
to go out to the DNS server to look up your own localhost!
"Much todo about nothing", eh?
-Jim Durham