[ale] pppd options
Gary MacKay
gary at edisoninfo.com
Mon Jul 29 15:37:32 EDT 2002
I'm using a RedHat 7.3 box for a dial-up access/firewall box at one
location. Works pretty well, but would like to make some changes. Does
pppd have any way to control the times that it dials in, how long it
stays dialed in, etc. Kind of like the old diald program used to do.?
The ISP this client is using is a pain. They cut them off at night and
will not let them dial in until 7am the next morning. Believe me, I've
tried to get the client to change ISP's, but.. well, that's another
story. I have 'persist' set so it immediately dials back in if it gets
knocked off-line for an unwanted reason, like during the day. They need
it to connect right back in. But, for some reason, it is not timing out
during the night. The 'idle' of 1200 (20 minutes) should drop the
connection right? The 'demand' should then wait for traffic to cause a
dial. They sware they turn all of their computers off at night so
nothing should be keeping it connected.
Bottom line, I need it to be dial-on-demand during the day, and not at
all during the night/weekends. I created a cron job to 'killall pppd'
for now and reload it in the morning, but that seems too brute force to
me. Just wondering if pppd had it's own options to handle this properly.
- Gary
The current /etc/ppp/options file is as follows:
lock
defaultroute
noauth
demand
persist
192.168.0.2:192.168.0.3
ipcp-accept-remote
ipcp-accept-local
holdoff 60
idle 1200
mtu 1500
mru 1500
ipcp-restart 1
ipcp-restart 1
user blocks
maxfail 0
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list