[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: repeated error



On Wed, 21 Jan 1998, Erez Doron wrote:
> > On Tue, 20 Jan 1998, Erez Doron wrote:
> > > > BTW diald is a hack. The correct way to solve your dialup problems, is to
> > > > use the kernel support for automatic establish on ppp send request
> > >
> > > how do you do that ?
> > >
> >
> > This has to do with auto loading modules (ppp.o), and the capacity of
...
> > is sent to the iface by the routing. But I may be wrong
> >
> > ...later
> > Go to altavista, and enter this for query: Linux PPP autodial. The 1st
> > doc you get is the one you want, but there is more.
> >
> > The most relevant URL is:
> >
> > http://www.cs.umsl.edu/~feldt/sluugs/meeting_notes/1997/aug/configppp.html
> >
> > I post this to the list, as it might interest a lot of people who are
> > tangled in the complications of the diald hack.
> >
> > regards,
> >         Peter
> 
> well, redhat4.2 comes with the script already in.
> ( /sbin/request-route is there, just create a chatfile, or hack the script)
> the operational diffrences between this method and diald is:
> 
> diald is more configurable
> diald can close connection when they is not used.
> 
> using kernel support will connect, but does not give indication
> if the ppp is still transfering , so the 'hangup' should be by other means
> ( i.e. online-time )

Consult your incomplete manuals for pppd. The option idle-disconnect is
not documented, but works from pppd2.2 pl 0 up. That is Slackware 3.0 up.
The option is documented in the URL I had indicated.

If you want an updated manual, I can upload mine into ftp2.linux.org.il
and you can pick it up from there (~12k gzipped). I don't know if newer
pppd manuals document the option. My manpage is v 1.15 for pppd 2.2 pl0
and does not have it (to get the manpage version, 'zless
/usr/man/man8/pppd.8.gz' - There is a RCS record in the header comments, 
in case you did not know).

Diald can close an idle connection only when it is idle. pppd knows that
it is idle before diald. Thus, pppd is in the best position to implement
this function.

(HINT: diald dates back to 1.2.13 days and before, when there was no
kerneld/request-route mechanism. diald used to do what kerneld does now. I
think that this is the real reason for which ppp.o can be compiled only as
a module, and not into the kernel, from 2.0.27 onwards at least) 

The file /sbin/request-route exists in all Linuxes (including Slackware),
since 3.0 (kernel 2.0.27) at least. 

BTW, if you have more than one ISP and if you have a preferred ISP for
connecting to a specific set of hosts, then this is the place to edit it
into. It shall select the correct chat script for the matching ISP based
on requested domain.

I have looked deeply into the matter of how a stuck modem can be reset and
there is none. I think that coding the idle timeout command into the chat
script of a modem known to hang often is a must. I don't know if it helps,
though.

> 
> so for now, I'm sticking with diald.
> 

If you like diald, you are welcome. I don't.

> Regards
> Erez.
> 

same,
	Peter