|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Aaron Freeman (afreeman
emprise.net)Date: Fri Feb 16 2001 - 13:56:33 CST
Duh. Of course. I couldn't find the autoload setting because its not
controlled by autoload--its controlled by 'set timeout'.
The answer is to either comment out autoload entirely (in which case
autoload will default to 0 0 5), or set it something like 0 0 0, which will
then force PPP to dial all modems up immediately for any traffic. The more
general 'set timeout' timer then controls all 4 modems globally, and will
disconnect all of them after a period of inactivity. Such as:
# set autoload 10 10 300
set timeout 300
Silly me.
Thanks for your help with this.
-Aaron
-----Original Message-----
From: owner-misc
openbsd.org [mailto:owner-misc
openbsd.org]On Behalf Of
Seth Arnold
Sent: Friday, February 16, 2001 3:10 AM
To: misc
openbsd.org
Subject: Re: Correcting timing for autodial on analog Multi-link PPP
setup
* Aaron Freeman <afreeman
emprise.net> [010216 02:29]:
> set autoload 5 1 300 # timer settings: <min%> <max%> <period>
>
> Its all working beautifully, except that I would like the system to bring
> all four modems up immediately when any activity occurs, and then leave
them
> all up for 30 minutes after the last activity.
Have you tried:
set autoload 0 0 0
? Of course, this might drive those poor modems crazy with starting and
stopping connections if it doesn't work as I hope it does...
> So, any ideas on how to separate the time-to-connect from the
> time-to-stay-connected?
You could try hacking the source to include a second timer. I bet this
is less easy than it may sound, but don't let my thought that it might
be ugly scare you off from looking at the source. :)
-- Earthlink: The #1 provider of unsolicited bulk email to the Internet.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]