Danny Thorp danny@thorp.fsworld.co.uk writes:
Any ideas?
Have you tried pppconfig, like the good book says? You might also find pppd's persist option some use. I don't think there's any reason for diald any more.
On 29-Aug-01 MJ Ray wrote:
Danny Thorp danny@thorp.fsworld.co.uk writes:
Any ideas?
Have you tried pppconfig, like the good book says? You might also find pppd's persist option some use. I don't think there's any reason for diald any more.
diald lets you control *when* connections are made. It also provides som filtering to prevent the connection from being raised for various classes of traffic. If you replace 'anyreason' by 'little reason', however, I agree with you. ---------------------------------- E-Mail: Raphael Mankin raph@panache.demon.co.uk Date: 29-Aug-01 Time: 13:37:43 ----------------------------------
on Wed, Aug 29, 2001 at 01:38:58PM +0100, Raphael Mankin scribbled:
find pppd's persist option some use. I don't think there's any reason for diald any more.
diald lets you control *when* connections are made. It also provides som filtering to prevent the connection from being raised for various classes of traffic. If you replace 'anyreason' by 'little reason', however, I agree with you.
pppd allows this too. admittedly it's not built into pppd. simply run a cronjob at the times you want to stop access (by killing pppd) and then when you wish to resume allowing ppp connections, restart it. you can also do this with atd so it's more scriptable. (this is how i get over certain isps two hourly disconnect.)
pppd supports the kind of filtering too via the active-filter option. http://uwsg.iu.edu/hypermail/linux/kernel/0009.0/0196.html might be necessary.
-
MJ Ray -
Raphael Mankin -
xsprite＠bigfoot.com