From: Paul Evans <pevans@catholic.org>
To: lartc@vger.kernel.org
Subject: [LARTC] double gateway - new thread
Date: Thu, 30 Jan 2003 23:58:45 +0000 [thread overview]
Message-ID: <marc-lartc-104397124523448@msgid-missing> (raw)
I've been subbing this list for a couple of months now, knowing this day would
come :-)
I too am trying to do an equalize/next hop for 2 adsl lines. At the moment
though I am testing with 1 2MB adsl modem and an ether connection to a switch
from a second 2MB line.
I am doing it from the *outside* via ssh, which makes it a little more
difficult, since when I mess up I lose access until I can get someone to
restart the network without my changes...
I began by using the example from lartc.org, combined with a cron to undo my
changes every half hour, but moved to following this page from sysadmin
magazine:
http://www.samag.com/documents/sam0201h/
For some reason I got a better sense of what I was trying to do from it, plus
it included a section on just where to place the new rules into the system
scripts. It did not say just where to place the section for ifup-routes
though.
I think I've got it pretty close, but since I just locked myself out again...
It's a mandrake 9.0 box and I didn't see where to prevent a default route from
being set when it brings up ppp0 on the adsl line. I sort of hoped that my
default routes would get set first and force the other to fail with the
Exists error. Since I couldn't find it, I don't know in what order it gets
run. I think that's where I messed up, but I can't get back in to read the
logs right now.
Also, the above article uses ip to route to the lan, and I had
intended/understood that I would masquerade to it later. Which is the correct
approach then? I will want to move on to tc when I finally get this part
working.
from the article:
advanced eth0 10.0.0.0/24 via 10.0.0.1 table 1
advanced eth0 10.0.0.0/24 via 10.0.0.1 table 2
advanced eth1 0/0 via 63.89.102.1 table 1
advanced eth2 0/0 via 65.3.17.1 table 2
Where eth0 is their lan and eth1/2 are isp. They have a new section in
ifup-routes grepping a file named static-routes for '^advanced'.
--
Regards, Paul Evans
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-01-30 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 23:58 Paul Evans [this message]
2003-01-31 0:33 ` [LARTC] double gateway - new thread William L. Thomson Jr.
2003-01-31 0:46 ` John Bak
2003-01-31 4:39 ` William L. Thomson Jr.
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-104397124523448@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.