From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Dual Internet Connection Routing
Date: Thu, 20 Dec 2001 08:40:46 +0000 [thread overview]
Message-ID: <marc-lartc-100883769724307@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100882802809659@msgid-missing>
On Wed, Dec 19, 2001 at 09:59:23PM -0800, K M wrote:
> +-------------+ +----linux--PC--+
> | DSL Router | | |
> | static IP |==<>--firewall |
> +-------------+ | | +----------+
> | <>== LAN Switch
> +-------------+ | | +----------+
> | DSL Router |==<>--firewall |
> | static IP | | |
> +-------------+ +---------------+
Nice ASCII!
The only easy way to do this is to have both DSL routers as default gateway
with the ip nexthop syntax, and do masquerading on both interfaces, and then
add policy routing to make sure that packets in a session that started on
ADSL router 1 *stay* on ADSL router one.
> Both the routers have static external IPs. I want the
> traffic to be equally divided between the two DSL
> lines and in case one of them is down, the other one
> should take up the entire load. The linux box will
This probably requires some CRON magic to detect when a link is down, and
you should then adjust your default gw.
> also function as a firewall. Now how should I go about
> configuring the system. Is it feasible to have two
> parallel firewalls on the same system ? How do I
> configure the routing to meet my requirements.
It is very feasible to have multiple firewalls on one linux machine.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-20 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-20 5:59 [LARTC] Dual Internet Connection Routing K M
2001-12-20 8:40 ` bert hubert [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-100883769724307@msgid-missing \
--to=ahu@ds9a.nl \
--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.