All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vernon A. Fort" <vfort@provident-solutions.com>
To: netfilter@lists.netfilter.org
Subject: Access to Internal server via public address
Date: 10 Dec 2003 13:33:17 -0600	[thread overview]
Message-ID: <1071084797.6081.35.camel@cosby> (raw)

Anyone,

  The Problem:  I have an alias public address DNAT'ed to and internal
address - normal and working

  What i need is to access this server using the PUBLIC address from an
internal workstation.  What I have:

	INTNIC = eth1
	EXTNIC = eth0

	INTERNALNET = 192.168.20.0/24

	FIREALLIP = 1.2.3.4
	DNATADDR = 1.2.3.5

  /sbin/iptables -I FORWARD -p tcp -i eth0 -o eth1 -d 192.168.20.0/24
--dport 22 -j ACCEPT
  /sbin/iptables -t nat -A PREROUTING -p tcp -d 1.2.3.5 -s !
192.168.20.0/24 --dport 22 -j DNAT 192.168.20.22:22

  I also have a SNAT for masquerading everyting going out

	/sbin/iptables -t nat -A POSTROUTING -s 192.168.20.0/24 -o eth0 -j SNAT
--to-source 1.2.3.4

  I have searched for a solutions longer than I care to admit.  Can
anyone give me an example on how to allow an internal ip address access
to another internal address via the DNAT'ed public address.

Vernon Fort




             reply	other threads:[~2003-12-10 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 19:33 Vernon A. Fort [this message]
2003-12-10 19:45 ` Access to Internal server via public address Antony Stone
2003-12-10 20:16 ` William Stearns
2003-12-10 20:25   ` Antony Stone
2003-12-10 20:55     ` William Stearns
2003-12-10 23:24       ` Home web server using front firewall Erick Sanz
2003-12-10 23:40         ` Antony Stone
2003-12-17 21:30           ` Erick Sanz
2003-12-17 21:56             ` Ian Hunter
2003-12-17 22:48             ` Antony Stone
2003-12-11  5:30       ` Access to Internal server via public address Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2003-12-10 20:36 Hoeschen, Chris
2003-12-11 10:45 ` Vernon A. Fort

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=1071084797.6081.35.camel@cosby \
    --to=vfort@provident-solutions.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.