From: Paul Evans <pevans@catholic.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Failover to modem assistance req
Date: Mon, 12 May 2003 04:56:46 +0000 [thread overview]
Message-ID: <marc-lartc-105271558805024@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105271146303087@msgid-missing>
On May 11, 2003 20:46 pm, gypsy wrote:
> My objective is to have the modem connection take over when the DSL
> fails. The DSL fails as the result of temperature and humidity
> fluctuations that cause a disconnect :(
I had one flakey modem for a few days. I set rp-PPPoE to:
CONNECT_TIMEOUT=0
from the default of 30. This makes it keep trying the connection infinitely
until it wins. I know this works because I attached a script to ip-up.local
to email us whenever the link went up which included that fact, plus the
grepped syslog info and the new ip(s).
I put that timeout=0 in all adsl connections now. Since I have my router
script set to run from ip-up.local, things get 'fixed' if another link comes
up anyhow.
It won't help the temp/humid prob, but it will bring it up as soon as possible
(at the expense of filling the log file with a bunch of failed attempts).
The above notion has been succesfull in overcoming both a flakey modem in one
case and an equally flakey cable in another.
This is only with pppoe of course, if you have a normal ether connection over
xdsl I don't have a fix for it, except to hang something from (I think
Julian's) dead gw patch. Or, you could do that anyhow I guess.
Another thing you could do that's kind of klugy, is to just ping gw, sleep x
until it fails and then bring up the dialup line and change the routing
tables and incorporate that kind of logic into ip-up until the xdsl comes
back and you can swx gw's.
Just one thought anyhow.
Oh, and re the temp/humid, you could graph the stuff over a week or so and
pick an alarm level and have something email/phone you when it's going bad.
You can get temp from sensorsd and match it to the problem. No simple/quick
way of getting humidity values without some wx h/w, but wouldn't be *that
expensive.
--
Regards, Paul Evans
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-12 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 3:46 [LARTC] Failover to modem assistance req gypsy
2003-05-12 4:56 ` Paul Evans [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105271558805024@msgid-missing \
--to=pevans@catholic.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.