Cary O'Brien wrote:
> > Cary O'Brien wrote:
> >
> > > > Is there any way of finding out who is initiating the link up and also
> > > > who is keeping the link up for diald?
> > > >
> > > You can get some of this information from two places:
> > >
> > > 1) If diald has a fifo enabled, you can tell it to provide state
> > > and timeout information. The dctrl script (in tcl) shows how
> > > this is done. I have used this in the past. There is also a
> > > diald-top program that is curses (?) program that does about
> > > the same thing.
> > >
> > > 2) I believe that with some debugging flags information about what
> > > brings up the link goes to syslog, hence to /var/log/messages. I've
> > > never done this. Some perusal of the documentation (I haven't upgraded
> > > past 0.16 yet -- if it ain't broke...) and the source may shed
> > > some light.
> >
> > hmmm, I think it you add "debug 24" to diald.conf for lots of messages and
> > details? right? I'm not really sure where it should go, but I read about it
> > somewhere.
> >
> > also is there a way, lets say that the link dies (meaning no traffic is going
> > in and out, like the connection got screwed up ie. someone picking up the
> > phone line) is there a way to detect this and tell diald to disconnect and
> > wait for the next request for an uplink?
> >
> I have the following in my ppp config file
>
> lcp-echo-interval 10
> lcp-echo-failure 3
>
> This should tell ppp to 'ping' (send an echo frame) to the other side
> once every 10 seconds, and to fail if 3 are dropped. diald will see that
> ppp died and try to retry.
>
> You may want to tune the diald retry timeout parameters (and the ppp parameters) if
> you want this to happen quicker.
>
> -- cary
thanks.. I'll give this a try
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
