From: Lukasz Hejnak <szift@wp.pl>
To: netfilter@lists.netfilter.org
Subject: Two ISPs, a bridge and iptables
Date: Mon, 13 Dec 2004 18:11:23 +0100 [thread overview]
Message-ID: <20041213171123.GA13902@samuraj> (raw)
Hi
I've been thinking about connecting two ISP's to a linux box and
then firewalling/masqrading that to a local net.
The solution I'm thinking of is:
- connect the ISP's to two different interfaces (say eth0/1)
- connect the local net via a third interface (eth3)
- bridge the two network interfaces into one (eth2)
- doing the rest of the iptables stuff using
eth2 as the internet and eth3 as the local net
some ascii art:
ISP#1 ISP#2
| |
===============================
| |
eth0 eth1
| |
---bridge---
eth2
|
iptables (linux box)
masq
|
eth3
|
===============================
|
local network
Now since I still have no playground for this to test, I've got these questions:
Would this solve the problem?
(local net have access at ISP1+ISP2 bandwidth to the internet)
Would the total load of connections outside be balanced
by iptables/bridge mechanism between the ISP's?
Is this the best/worst/fastest/slowest way to do this?
How will the things change when one of the ISP's fail?
--
with regards
Lukasz Hejnak
szift@wp.pl
next reply other threads:[~2004-12-13 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:11 Lukasz Hejnak [this message]
2004-12-13 18:03 ` Two ISPs, a bridge and iptables Jason Opperisano
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=20041213171123.GA13902@samuraj \
--to=szift@wp.pl \
--cc=netfilter@lists.netfilter.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.