From: Christoph Simon <datageo@terra.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] route with different metric
Date: Wed, 26 Sep 2001 13:39:27 +0000 [thread overview]
Message-ID: <marc-lartc-100151157622422@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100150978014261@msgid-missing>
On Wed, 26 Sep 2001 15:10:35 +0200
"Christian Lox" <lox@eq-media.de> wrote:
> Hi everyone!
>
> Sorry if this is a FAQ but I did not find a searchable archive.
>
> What I am planning to do:
> 2 different connections to 2 different ISPs.
> One is handled by an ISDN card, one via ethernet to their router
> (DSL).
> We want to use the DSL line; only if this fails we need the ISDN
> line.
> I played around with the metrics but could not get it to work.
I'm trying to find a solution for this very situation since a long
time, but wasn't able to do so. What is working for me now is a small
daemon I wrote which essentially replaces ipup and ipdown.
Initially it reads the standard /etc/network/interfaces files, paying
attention to an additional parameter of priority which is commented
out. Then, the interfaces are set up the normal way, but the routes
are set with mask /32 just to reach the gateway and no default
route. Then, every 60 seconds, a single ping is sent to the gateway of
each of the external interfaces, marking it either up or down. After
that, the priority value is checked and the program chooses that with
the highest priority. If that is also marked active, nothing else is
done, but if it wasn't active, the default route is put to that
interface and the firewall script is reinitialized. Of course, if the
active interface becomes down, the default route is removed.
This works fine, but it's a real pitty that I can't use both
interfaces in a balanced way as this would effectively duplicate my
bandwidth while both are up. Another (small) problem with this
approach is, that switching interfaces automatically stops operators
from realizing that a line is not working for to take corrective
action. So I decided to send an email in such case, which of course
fails if both interfaces are down because I'm geografically far from
these networks. But then, operators do realize that something is
wrong.
I wrote this program some days ago and it's really a dirty hack, so I
doubt the code would be more useful than this description.
I don't have experience with Cisco routers, but was told that load
balancing to two or more independent external links is possible with
them. So I guess, somehow it should also be possible with Linux. If
somebody could shed light on this, I would be really greatful.
--
Christoph Simon
datageo@terra.com.br
---
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
NO CARRIER
.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-09-26 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 13:10 [LARTC] route with different metric Christian Lox
2001-09-26 13:13 ` bert hubert
2001-09-26 13:39 ` Christoph Simon [this message]
2001-09-26 13:45 ` Juri Haberland
2001-09-26 13:53 ` Juri Haberland
2001-09-26 14:10 ` bert hubert
2001-09-26 14:37 ` Juri Haberland
2001-09-26 18:05 ` Adrian Chung
2001-09-26 20:53 ` bert hubert
2001-09-26 21:16 ` Adrian Chung
2001-09-27 7:44 ` Juri Haberland
2001-09-27 22:40 ` Adrian Chung
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-100151157622422@msgid-missing \
--to=datageo@terra.com.br \
--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.