[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: repeated error
Peter L. Peres 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
> kerneld to execute an action before that. I don't know how exactly it is
> done, I will look in dejanews fot that and let you know. I ran into a
> message that described such a setup. It works for sure. As I remember it,
> ppp.o is a module, with dialup using the scripts it calls by itself. pppd
> is passed options to time out the link. To dial, a packet is sent to the
> ppp iface. kerneld loads the module and this causes dialling. When the
> link is not used, pppd times out and hags up. Then kerneld notices that it
> is not running, and removes the module. The dialing is controlled by what
> 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 )
so for now, I'm sticking with diald.
Regards
Erez.