From: Joe Ruddy <jruddy@novapointe.com>
To: netfilter@vger.kernel.org
Subject: (unknown)
Subject:
Date: Thu, 3 Jan 2008 13:57:48 -0800 [thread overview]
Message-ID: <00b301c84e53$ae114a80$9604000a@jrdesktop> (raw)
Hello,
We are moving to a Co-Location center and will need to forward all traffic
for all our IP to our new IP addresses.
As an example our block is 12.24.15.0/24
Our new block will be 54.64.18.0/24
If we have a webserver at 12.24.15.24 I would like all requests to
12.24.15.24 to be forwarded to 54.64.18.24 where the new machine will be
located.
If we have a mailserver at 12.24.15.19 I would like all requests to
12.24.15.19 to be forwarded to 54.64.18.19 where the new machine will be
located.
I add one rule ..."iptables -t nat -A PREROUTING -d 12.24.15.24 -j DNAT --to
54.64.18.24"
If I try to ssh or go to the website hosted there I get nothing. I can see
that the requests arrive at 54.64.18.24 by looking at the logs.
Any ideas?
Thanks
Joe
Joe Ruddy
Director of Technology
Novapointe LLC
909-930-3062 x2738
jruddy@novapointe.com
next reply other threads:[~2008-01-03 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 21:57 Joe Ruddy [this message]
2008-01-03 22:22 ` Martijn Lievaart
-- strict thread matches above, loose matches on Subject: below --
2017-08-11 22:09 (unknown), Chris
2011-11-07 14:23 (unknown) Tarak Ranjan
2009-01-02 19:29 (unknown), Jorge Bastos - Decimal
2008-12-09 12:14 (unknown), Martin Spinassi
2008-10-31 7:14 (unknown), Jianqing Zhang
[not found] <S1752389AbYJDKwq/20081004105246Z+121@vger.kernel.org>
2008-10-04 11:20 ` (unknown) Sebastian Seemann
2008-07-27 1:11 (unknown), David Boulding
2008-03-07 8:06 (unknown) Alberto Díez
2008-01-11 12:31 (unknown), Videal ,)
2008-01-05 5:34 (unknown), Bikash Bhattarai
2007-12-11 18:39 (unknown) Ryan Rodriguez
2007-11-15 5:24 (unknown), 李伟华
2007-09-21 22:33 (unknown), David Boulding
2007-09-15 23:15 (unknown) "Mario Hülsegge"
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='00b301c84e53$ae114a80$9604000a@jrdesktop' \
--to=jruddy@novapointe.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox