All of lore.kernel.org
 help / color / mirror / Atom feed
From: O-Zone <liste@zerozone.it>
To: netfilter@lists.netfilter.org
Subject: DMZ to DMT through ROUTER problem !
Date: Thu, 20 May 2004 13:18:29 +0200	[thread overview]
Message-ID: <200405201318.34706.liste@zerozone.it> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,
i've a big problem. Here's a little diagram:

[INTRANET 10.0.0.0/24]-------------+
                                                      +--[ROUTER]--(NET)
[DMZ SERVER A - 192.168.0.2]----+
[DMZ SERVER B - 192.168.0.3]----+

Each DMZ server is mapped to it's PUBLIC IP. For example:

151.8.47.A ----> 192.168.0.2
151.8.47.B ----> 192.168.0.3

and all work perfectly !!!

The problem is when, from 192.168.0.2, i try to connect to 151.08.47.B (trat's 
mapped to 192.168.0.3): packets die on ROUTER.

Here's my IPTABLES configuration:

[.....]
#
# 3.1 Required proc configuration
#

echo "1" > /proc/sys/net/ipv4/ip_forward

#
# 3.2 Non-Required proc configuration
#

echo "1" > /proc/sys/net/ipv4/conf/all/rp_filter
#echo "1" > /proc/sys/net/ipv4/conf/all/proxy_arp
#echo "1" > /proc/sys/net/ipv4/ip_dynaddr
echo "1" > /proc/sys/net/ipv4/conf/all/accept_source_route

[....]
#
# 4.3.8 POSTROUTING chain
#

$IPTABLES -t nat -A POSTROUTING -s 10.0.0.0/24 -j MASQUERADE

# This is my TRY :-( but don't work...
$IPTABLES -t nat -A POSTROUTING -o $DMZ_IFACE -s 192.168.0.0/24 -d 151.8.47.A 
- -j MASQUERADE
$IPTABLES -t nat -A POSTROUTING -o $DMZ_IFACE -s 192.168.0.0/24 -d 151.8.47.B 
- -j MASQUERADE

# Perhaps the same as the first
$IPTABLES -t nat -A POSTROUTING -o $INET_IFACE -j SNAT --to-source $INET_IP

Someone can help me ?

Please ! Oz


- -- 
Legge di Eagleson:
	Qualsiasi tuo personale codice sorgente che non e' piu' stato
	guardato da sei o piu' mesi potrebbe benissimo essere stato
	scritto da qualcun altro.  (Eagleson e' un ottimista; il numero
	reale e' piu' vicino alle tre settimane.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFArJQHYuBSFbgkEysRAsMqAKDYL9wufFI1uEVNubiBhsdlLVHs+gCgjwq3
JASN8hPUrFKObgR4MzAPZ0k=
=hVW2
-----END PGP SIGNATURE-----



             reply	other threads:[~2004-05-20 11:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 11:18 O-Zone [this message]
2004-05-20 12:30 ` DMZ to DMT through ROUTER problem ! Antony Stone
2004-05-20 12:54   ` O-Zone
2004-05-20 13:22     ` Antony Stone
2004-05-20 14:37       ` O-Zone
2004-05-20 14:45         ` Antony Stone
2004-05-20 14:58           ` O-Zone
2004-05-20 15:07             ` Antony Stone
2004-05-20 15:53               ` O-Zone
2004-05-20 16:07                 ` Antony Stone
2004-05-20 16:32                   ` O-Zone
2004-05-20 17:34                     ` Antony Stone
2004-05-20 17:44                       ` Antony Stone
2004-05-21  9:30                         ` O-Zone
2004-05-21 10:19                           ` Antony Stone
2004-05-21 14:08                             ` O-Zone

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=200405201318.34706.liste@zerozone.it \
    --to=liste@zerozone.it \
    --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.