[plug] pppd redialling too often
Dave T Burbidge
dave969 at iinet.net.au
Tue Nov 23 21:00:56 WST 1999
Steve,
I'm also with iiNet (that 10 min's can be a killer :(
'holdoff 600' works for me (even more annoying when I forget about it, and the
modem kicks in ten minutes later)
Sorry, no idea which version of pppd I'm running, but my full line is...
pppd /dev/modem 56000 connect 'chat <insert own script>' crtscts noipdefault
defaultroute usepeerdns modem proxyarp ktune :203.0.178.191 demand holdoff 600
persist
Note that the LINUX box is on a LAN, and handles the 'net connection for all
three PC's (why DEMAND & PERSIST are there - the IP address is one that pppd
listens to at my end - when something tries to talk to that, it dials up). The
other parameters can be found under MAN...
For a really silly thought, make sure you have the closing "'" in the correct
place on the CONNECT CHAT bit - is the HOLDOFF parameter on the wrong side (it
should be outside) - don't worry, I tried something similar myself when setting
up mine...
Hope this helps...
Dave!
--
Home : http://www.iinet.net.au/~dave969/
This Murphy person has a lot to answer for!
Steve Baker wrote:
> Thanks for the ideas, and while both are obviously effective, does anybody
> have any idea why the documented 'holdoff' option for pppd doesn't work?
> Does the documentation need to be recompiled?
>
> bakes
> --
> Steve Baker (aka sbaker at icg.net.au) -- Integra Consulting Group
> http://www.icg.net.au
> Open your mind, then look at http://www.nexusmagazine.com
> -----Original Message-----
> From: Brad Campbell <brad at seme.com.au>
> To: plug at linux.org.au <plug at linux.org.au>
> Date: Friday, 19 November 1999 12:38
> Subject: Re: [plug] pppd redialling too often
>
> >>
> >> I had a similar requirement recently (iinet wnt a 10 minute delay unless
> >> you've overrun your 200 hours, when they want 30 !), and ended up by
> >> putting together a quick and dirty shell script that connects, waits to
> be
> >> disconnected, sleeps 10 minutes and then goes round the loop again (but
> >> only up to the usual 'going home' time for the client).
> >>
> >> Like I said, grubby, but it works very well.
> >>
> >> Paul
> >
> >I did it slightly differently.
> >In my ip-down script, I do an
> >echo block > /var/run/diald/diald.fifo
> >and I put a file called nodial in /etc/ppp
> >I then set an at command to run a file called /var/diald/unblock
> >11 minutes after NOW.
> >
> >/etc/diald/unblock just unblocks diald and removes the nodial file.
> >The ppp-dial script check for the nodial file, and aborts if it exists.
> >It also checks for a file called nightdown.
> >
> >I then have a cron entry to place nightdown in /etc/ppp at 6.15pm
> >and remove it and run the unblock script at 7.45 am.
> >This effectively gives me a connection all day during working hours
> >with no wasted phone calls at night or on the weekend.
> >It's a little convoluted, but it works exceedingly well..
> >
> >
> >--
> >Brad....
> >"The ultimate result is that some innovations that would
> >truly benefit consumers never occur for the sole reason
> >that they do not conincide with Microsoft's self-interest"
> >- Judge Thomas Penfield Jackson
> > /"\
> > \ / ASCII RIBBON CAMPAIGN
> > X AGAINST HTML MAIL
> > / \
> >
More information about the plug
mailing list