Re: diald / ppp routing problems
- To: Debian-User <email@example.com>
- Subject: Re: diald / ppp routing problems
- From: Joe Stewart <firstname.lastname@example.org>
- Date: Thu, 6 Nov 1997 20:43:58 -0600 (CST)
- Message-id: <Pine.LNX.3.96.971106203637.2823A-100000@bullhead>
- In-reply-to: <18.104.22.168.19971107082404.007a36d0@mail>
I have a similar? problem. After a system crash from disk errors, a
working diald/ppp setup will not connect correctly. The error message
received is "serial line looped back". I could not find a description of
this message anywhere. After uninstalling diald and using "pon", I am
connected now. If I execute "poff" it returns that there is more than one
pppd running, but "ps -ax" reports only one.
Regarding the "files dns" line in nsswitch.conf, it worked fine with this
line in the file previously, but I removed the dns entry with no help.
Any help would be appreciated.
On Fri, 7 Nov 1997, Joost Kooij wrote:
> > > There were some problems reported with the /etc/nsswitch.conf.
> > > The networks line says " files dns" which means that when resolving a
> network address, libc will try first /etc/networks, then ask on DNS.
> > > However route tries to resolve the net diald passes to it and blocks in
> there (the DNS server cannot be contacted because there's no route to it,
> and the route cannot be established because the net has to be resolved).
> > >
> > > Try removing the dns entry from the networks line of /etc/nsswitch.conf.
> > >
> > > Anyways, this is problematic to have this networks line with dns, and
> > > a future version of base-files is supposed to fix this.
> Is there a place where I can find documentation about /etc/nsswitch.conf?
> I couldn't find any man pages, info documents or files in
> /usr/doc/base-files that covers what it is for or what it does.
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> email@example.com .
> Trouble? e-mail to firstname.lastname@example.org .
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .