From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: nat on multihomed server
Date: Sat, 24 Jan 2004 09:23:20 +0000 [thread overview]
Message-ID: <200401240923.21218.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <1164.203.131.168.150.1074915322.squirrel@www.localgovernance.net.ph>
On Saturday 24 January 2004 3:35 am, Sandy T. Santos wrote:
> our campany has two internet links from different isp's. we then use both
> of these to host the company's webserver. what i want is that the
> webserver maybe accessible by coming from my isp1 link or my isp2 link. i
> know that i need to set up my dns to have two ip addresses that points to
> my linux box and then DNAT that connection towards my webserver. what i
> don't know is what's the iptables script gonna look like for the SNAT
> reply. how would i be able to determine that the request that came in to
> my webserver originated from my isp1 or isp2 link so that the reply would
> be SNAT'ed to that interface?
I suggest you give your webserver two internal addresses on the same interface
(eg 192.168.1.100 and 192.168.1.101, or whatever fits with your addressing
scheme), and DNAT one public address to the first, and the other public
address to the second.
Your web server applications should be able to listen on multiple addresses,
and it will reply from the address which was contacted, therefore the
automatic SNAT rules which netfilter will do for you behind the scenes will
work. No need for manual SNAT rules.
Regards,
Antony.
--
My New Year's resolution is not to make any resolutions I can't keep.
I'm wondering whether I've failed already.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-01-24 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 3:35 nat on multihomed server Sandy T. Santos
2004-01-24 9:23 ` Antony Stone [this message]
2004-01-24 14:44 ` Alexis
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=200401240923.21218.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox