On 28 Sep, Mike Childers wrote:
Sorry for y mismatched the subject, and thanks for this good
information.
Sometimes English's a fight for me ....
Niko
> Diald may be another way of doing the same thing and I have had no
> experience using this command, but pppd now has the capability of doing the
> demand function for itself using the 'demand' option in the pppd
> configuration. This 'demand' option is what we were talking about. pppd is
> started with the 'demand' option and will wait to dial out ( using its
> 'connect' option and CHAT or some other dialer program) until it has a
> packet to send. It will then hang up after a specified idle timeout period
> and then redial when another packet needs to be sent. Clifford Kite sent a
> sample script that shows how to do this without using diald. Diald sounds
> like a roundabout way of acomplishing the same thing since it uses a
> different interface than ppp0 and it might be worth checking into the new
> version of pppd.
>
> By the way, all hail to the programming staff that maintain and develop the
> pppd package. I have been using this package for myself and in a few
> businesses who have come to count on it on a daily basis. it has come a long
> way since I first used it several years ago and I would sooner put in a
> linux box as a router to the internet or another network using pppd than try
> to use a RAS style connection from Windows 95 or NT. A little more work, a
> LOT better results!
>
> Thanks guys!
>
> Mike Childers
>
>> On 27 Sep, Mike Childers wrote:
>> > I haven't used the demand dialing feature yet, but my understanding of
> the
>> > feature is that the only thing that is automatic is the actual dialing
>> > feature. The pppd daemon and the interface need to be up and running,
>>
>> No, pppd will wake up on the diald "demand", the only interfaces that's
>> up is tap0 or sl0 (and of course lo + eth0 if you have one). Diald will
>> monitor tap0 to see if it's necessary to fire pppd up and then it will
>> monitor pppd himself (this is the way i understand it...)
>> > waiting for a packet to tell it to dial out. It is also my understanding
>> > that if you use the 'demand' option, pppd does not automatically dial
> out
>> > upon startup. You could then have it start on bootup and remain up until
> it
>> > is ready to dial out.
>>
>> yes, diald is started at the boot
>>
>> > This assumes that you allow pppd to initiate the
>> > dialing and not have a dialer dial out and then start up pppd.
>>
>> pppd never initiate dialing, it's diald's job
>>
>> > The demand option implies the 'persist' option, which allows pppd to
> remain running
>> > after the connection times out to wait for another wakeup packet.
>> >
>> > It only makes sense that there has to be an interface running and a
> route
>> > pointing to it in order for a 'wakeup' packet to know that it needs to
> go
>> > out that interface.
>>
>>
>> Niko
>>
>>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
