redundant office of redundancy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy! As you can tell from my subject line, I am interested today in making
sure that I can always surf por^W^Wserve webpages. My business (consulting &
small-time webhosting) is dependent on my always having an internet
connection. Currently, I have a fairly stable dsl line that serves my needs,
but some stupid redback issues on my isp's side have made me wary. I figure
the chances of both a dsl line and cable going out at the same time are
fairly small, and throwing $50 a month at the problem is acceptable. Now, as
I'm planning on doing this, it begs the question(s): 1) how to aggregate the
bandwidth of both pipes into one, transparently (I will be using two
computers as well, might as well do it right); 2) how do you go about setting
up "failover", such that if one of the machines drops out, the other takes
over dns/mail/web?
I know some of you out there are about to exclaim "Get your isp to do this,
idiot!" Well, I'm large enough to seriously look at this, but small enough
(and geeky enough) that I'd really like to take care of it myself. I have a
decent background in setting up linux as a firewall/proxy/nat box, and a
basic understanding of "real" routing. Pointers, hints, tips, all are
welcomed gratefully.
To sum up: currently, my setup is 2 machines hot to the 'net, the rest nat'ed
off, all using 1 dsl and a block of ips, all nat routing through 1 of the
machines. I would like to end up with dual-connections, bandwidth aggregated
through both the machines, and failover for high-priority services.
Thanks!
- --
D.A.Bishop
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8hozkEHLN/FXAbC0RAqILAJ4+m/vgTuCluGdDjP+zj9U24QxBQgCfdNTg
4wcJpD5lrFxyV6B6kTfywh8=
=T1Ff
-----END PGP SIGNATURE-----
Reply to: