Re: diald problem

["David B.Teague" <dbt@cs.wcu.edu>]

On Mon, 17 May 1999, Pollywog wrote:

 
> I had to reinstall Linux, and I did not have everything I needed
> on my backup floppies.  I thought I had backed up all my config
> files, so I believe I accidentally deleted stuff. 
 
> Anyhow, when my ISP drops me during long downloads, I am allowed
> to come right back, and diald took care of this for me until
> now, because I lost the diald.options file I was using.  There
> is an option (I have checked the man pages but cannot find it)
> that I had set to four seconds so that if I get disconnected, I
> come back in 4 seconds, not 30.  Anyone know what that option
> is?  I have redial-timeout, but that does not seem to be it.  I
> am doing lots of this stuff by trial and error.

Pollywog

Did you get an answer to this? 

I do not use diald, but there are option under ppp that may
help you, so on the off chance that this will do you some 
good, I'm sending it on.

My system reconnects if the line is dropped for a couple of
minutes. I looked in my /etc/ppp/peers/provider and found the last
command is persist.

Here are items from the pppd man page, and from /etc/ppp/options. 
Can these be used to detect disconnect and after 4 seconds effect
reconnect?

>From the man 8 pppd page:

       lcp-echo-failure n
              If this option is given, pppd will presume the peer
              to be dead if n LCP echo-requests are sent  without
              receiving a valid LCP echo-reply.  If this happens,
              pppd will terminate the connection.   Use  of  this
              option  requires a non-zero value for the lcp-echo-
              interval parameter.  This option  can  be  used  to
              enable pppd to terminate after the physical connec-
              tion has been broken (e.g., the modem has hung  up)
              in situations where no hardware modem control lines
              are available.

       lcp-echo-interval n
              If this option is given,  pppd  will  send  an  LCP
              echo-request  frame  to  the  peer every n seconds.
              Normally the  peer  should  respond  to  the  echo-
              request  by sending an echo-reply.  This option can
              be used with the lcp-echo-failure option to  detect
              that the peer is no longer connected.
 
I find these settings in the /etc/ppp/options file:

# If this option is given, pppd will send an LCP echo-request frame to
# the peer every n seconds. Under Linux, the echo-request is sent when
# no packets have been received from the peer for n seconds.
# Normally the peer should respond to the echo-request by sending an
# echo-reply. This option can be used with the lcp-echo-failure
# option to detect  that the peer is no longer connected.
lcp-echo-interval 30
 
# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4
 
--David
David Teague, dbt@cs.wcu.edu
Debian GNU/Linux Because software support is free, timely,
                 useful, technically accurate, and friendly.
		 (Hoping this is useful!)