From: guillaume <guillaume.riviere@hcm.vsl-vn.com>
To: iptables <netfilter@lists.netfilter.org>
Subject: Routing, SNAT and two ISPs
Date: Tue, 10 Aug 2004 16:18:10 +0700 [thread overview]
Message-ID: <411892D2.6010904@hcm.vsl-vn.com> (raw)
Hi all,
Well, it's seams to be a little bit more complicated than
I thought to loadbalance Internat connection between 2 (different) ISP
lines ...
Here is my problem:
Basically, I need to connect my office to 2 differents ISP (different
gateways and different DNS ). My linux box is a 3 NICs Box. The problem
is that, for the first ISP, I don't have static Addresses.
So, I would like to loadbalance, "route" and NAT all my internals Addresses
through thoses 2 ISP except for some addresses and some port numbers
which will use
only the ISP2.
I would like also to detect dead gateway (maybe I ask for to much ...).
My problem is that SNAT is POSTROUTING. I am lose ...
I don't know if I have to deal with iptable2 loadbalancing or if I can do
this only with netfilter.
Maybe in a first part, I just would like to "statically loadbalance" my
connections.
I mean, just put rules to (for example)
- route http packets to my first ISP and ssh packets to my second ISP,
- route packets from my internals IP 10.0.0.2-100 to ISP 1
- route packets from my internals IP 10.0.0.101 to ISP2
(all with NAT, of course)
After, I will deal with a real loadbalancing for a part of my internal
IP and
for some protocols.
Any Help will be very appreciated,
Thank you in advance,
Guillaume
next reply other threads:[~2004-08-10 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 9:18 guillaume [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 12:15 Routing, SNAT and two ISPs Jason Opperisano
2004-08-12 1:11 ` Ming-Ching Tiew
2004-08-13 0:38 ` guillaume
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=411892D2.6010904@hcm.vsl-vn.com \
--to=guillaume.riviere@hcm.vsl-vn.com \
--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.