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
