From: Andrew Beverley <andy@andybev.com>
To: Dimitri Yioulos <dyioulos@onpointfc.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
"DiCecca, Caitlin" <cdicecca@onpointfc.com>
Subject: Re: Dual WAN setup redux
Date: Thu, 02 Feb 2012 23:11:13 +0000 [thread overview]
Message-ID: <1328224273.18690.29.camel@andrew-desktop> (raw)
In-Reply-To: <201202021252.07673.dyioulos@onpointfc.com>
On Thu, 2012-02-02 at 12:52 -0500, Dimitri Yioulos wrote:
> I changed the ip addy of the test server to 192.168.1.11, back on the
> DMZ subnet. I now have partial success, as I can ping the gateway
> (75.x.x.30).
So can I :)
> I think I have the correct SNAT and DNAT rules to reach this
> on port 80, but I can't reach it via 75.x.x.27, which is its external
> address. Nor can I ping it.
You need to add the .27 address to the interface that is connected to
the 75.144.186.30 Cisco router (eth3?).
You should then be able to ping 75.144.186.27 from the internet. Once
that is working, it should just be a matter of adding the DNAT rule for
192.168.1.11 to forward from eth3.
> I don't know if it's helpful, but I've attached what I hope is a new, better
> network map.
That's pretty good, but missing a few helpful things such as the
interface names, which I think you had on previous diagrams.
Andy
next prev parent reply other threads:[~2012-02-02 23:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 17:52 Dual WAN setup redux Dimitri Yioulos
2012-02-02 23:11 ` Andrew Beverley [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-27 23:03 Dimitri Yioulos
2012-01-31 1:50 ` Lloyd Standish
2012-01-31 17:15 ` Andrew Beverley
2012-02-01 16:51 ` Dimitri Yioulos
2012-02-01 18:49 ` Andrew Beverley
2012-02-01 19:46 ` Dimitri Yioulos
2012-02-01 20:25 ` Andrew Beverley
2012-02-01 20:35 ` Andrew Beverley
2012-02-01 22:08 ` Dimitri Yioulos
2012-02-01 23:32 ` Andrew Beverley
2012-02-02 7:35 ` Andrew Beverley
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=1328224273.18690.29.camel@andrew-desktop \
--to=andy@andybev.com \
--cc=cdicecca@onpointfc.com \
--cc=dyioulos@onpointfc.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