From: "Tim" <twr@bellsouth.net>
To: iptables-list <netfilter@lists.samba.org>
Subject: Syntax/NAT OUTPUT
Date: Tue, 9 Jul 2002 15:59:44 -0700 [thread overview]
Message-ID: <000801c2279c$6e2364f0$4fcf3cd0@nebuchadnezza> (raw)
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]
Scenario: router eth0 to Fwall 192.168.2.2
Fwall eth0 from router 192.168.2.1
Fwall eth1 from DMZ 172.16.1.1
Fwall eth2 from LAN 192.168.1.1
My understanding of concepts of filtering and nat
Pinging from the router eth0 thu Fwall eth2 to LAN, it first goes through PREROUTING nat table then the filter INPUT----this the path it takes to get to any box in the LAN .....yes ?
To get a reply from this ping it must go thru the NAT OUTPUT then filter OUTPUT.....this is my understanding of the return path for this ping from the router eth0.....is this correct so far ? If so what would be the syntax for the NAT OUTPUT in order to get and echo-reply. This is the portion of the script for my NAT configuration.
Mind, ppl, I just started leaning this........any suggestion will most certainly be welcomed and appreciated...TIA...
--snip--
## PREROUTING ##
iptables -A PREROUTING -t nat -s 192.168.2.0/24 -d 192.168.1.0/24 -j DNAT --to 192.168.1.0
## POSTROUTING ##
iptables -A POSTROUTING -t nat -s 192.168.1.0/24 -d 192.168.2.0/24 -j SNAT --to 192.168.2.0
#
## NAT OUTPUT ##
iptables -A OUTPUT -t nat -s 192.168.1.0/24 -d 192.168.2.0/24 -j ACCEPT ## It looks like this is where the problems is at, syntax ?? ##
#
#
## FORWARD traffic between INTERNAL and DMZ
iptables -A FORWARD -p icmp --icmp-type echo-request -j ACCEPT
iptables -A FORWARD -p icmp --icmp-type echo-reply -j ACCEPT ## This should enable me to forward ping request and replies
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT ## universally.....yes...??##
#
## INPUT manage traffic coming into this box ##
#iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i eth2 -p icmp -j ACCEPT
iptables -A INPUT -i eth0 -p icmp -j ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -i eth0 -s 192.168.2.2 -d 192.168.1.0/24 -p icmp -j ACCEPT ## I configured this in order to ping the eth0 on the router ##
# ## and it works fine.....this is where it stops, it has no way ##
## OUTPUT manage traffic going out of this box ## ## to reply to this packet hence forth my dilemma ##
#iptables -A OUTPUT -o eth2 -s 192.168.1.0/24 -p icmp --icmp-type echo-request -j ACCEPT
#iptables -A OUTPUT -o eth2 -s 192.168.1.0/24 -p icmp --icmp-type echo-reply -j ACCEPT
#iptables -A OUTPUT -o eth1 -s 172.16.1.0/24 -p icmp --icmp-type echo-request -j ACCEPT
#iptables -A OUTPUT -o eth1 -s 172.16.1.0/24 -p icmp --icmp-type echo-reply -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -o eth0 -s 192.168.1.0/24 -j ACCEPT
--snip--
---
Tim Rodriguez -- Mia/Fla.
Network Security Student
---
I prefer to be a dreamer
among the humblest,
with visions to be realized,
than a lord among those without
dreams and desires.
[-- Attachment #2: Type: text/html, Size: 6430 bytes --]
next reply other threads:[~2002-07-09 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 22:59 Tim [this message]
2002-07-09 20:27 ` Syntax/NAT OUTPUT Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 21:58 George Vieira
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='000801c2279c$6e2364f0$4fcf3cd0@nebuchadnezza' \
--to=twr@bellsouth.net \
--cc=netfilter@lists.samba.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