From: "Pierre Gillet" <gpg__gpg@hotmail.com>
To: netfilter@lists.netfilter.org
Cc: gpg.gpg@caramail.com
Subject: problem with forward/nat
Date: Sun, 07 Mar 2004 04:13:30 +0100 [thread overview]
Message-ID: <BAY1-F168WzqJX7rVGS00004a39@hotmail.com> (raw)
hello,
i have a small private network, 192.168.1.0 on eth1
public network on eth0. the server running a dhcp server for private
network.
system: SuSE 9.0Pro, iptables 1.2.8
my script:
echo "1" > /proc/sys/net/ipv4/ip_forward
#vidage des tables
iptables -F
iptables -X
#policies par defaut
iptables -P INPUT DROP
iptables -P OUTPUT DROP
iptables -P FORWARD DROP
#autorise boucle locale
iptables -A OUTPUT -o lo -m state --state RELATED,ESTABLISHED,NEW -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 80 -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 443 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth1 -d 192.168.1.0/24 -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 23 -j ACCEPT
iptables -A INPUT -i lo -m state --state RELATED,ESTABLISHED,NEW -j ACCEPT
iptables -A INPUT -i eth0 -p udp --sport 53 -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 80 -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 443 -j ACCEPT
iptables -A INPUT -i eth1 -s 192.168.1.0/24 -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 23 -j ACCEPT
#forward
iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
iptables -A FORWARD -s 192.168.1.0/24 -j ACCEPT -o eth0
#iptables -A FORWARD -i eth0 -o eth0 -m state --state ESTABLISHED,RELATED -j
ACCEPT
modules are here:
ls /lib/modules/`uname -r`/kernel/net/ipv4/netfilter/
ip_queue.o ipt_ULOG.o ipt_pkttype.o
ip_tables.o ipt_ah.o ipt_psd.o
arp_tables.o ipchains.o ipt_conntrack.o ipt_state.o
arptable_filter.o ipfwadm.o ipt_dscp.o ipt_string.o
ip_conntrack.o ipt_DSCP.o ipt_ecn.o ipt_tcpmss.o
ip_conntrack_amanda.o ipt_ECN.o ipt_esp.o ipt_tos.o
ip_conntrack_ftp.o ipt_LOG.o ipt_helper.o ipt_ttl.o
ip_conntrack_irc.o ipt_MARK.o ipt_iplimit.o ipt_unclean.o
ip_conntrack_tftp.o ipt_MASQUERADE.o ipt_length.o iptable_filter.o
ip_nat_amanda.o ipt_MIRROR.o ipt_limit.o iptable_mangle.o
ip_nat_ftp.o ipt_REDIRECT.o ipt_mac.o iptable_nat.o
ip_nat_irc.o ipt_REJECT.o ipt_mark.o
ip_nat_snmp_basic.o ipt_TCPMSS.o ipt_multiport.o
ip_nat_tftp.o ipt_TOS.o ipt_owner.o
problem:
pc firewall can acces on web
pc firewall can acces in private network
private network can acces in pc firewall
private network CAN'T acces on web
i sniff on eth0 and eth1, request from private network are sniffed in eth1
but not transmiet on eth0, it cant go out.
can you help / explain to me?
sorry for my very bad english and thank you for your help
Pierre
gpg__gpg@hotmail.com
_________________________________________________________________
Calendrier Pirelli, les top modèles de mars...
http://automobile.fr.msn.be/pirelli2004/mars2/
next reply other threads:[~2004-03-07 3:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 3:13 Pierre Gillet [this message]
2004-03-07 9:26 ` problem with forward/nat Antony Stone
2004-03-07 9:46 ` Antony Stone
2004-03-07 14:47 ` Brad Morgan
2004-03-07 15:03 ` Antony Stone
2004-03-07 15:57 ` Brad Morgan
2004-03-07 18:24 ` Fabian Hartmann
2004-03-07 18:37 ` Antony Stone
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=BAY1-F168WzqJX7rVGS00004a39@hotmail.com \
--to=gpg__gpg@hotmail.com \
--cc=gpg.gpg@caramail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox