From: Anders Fugmann <afu@fugmann.dhs.org>
To: Dan Egli <dan@shortcircuit.dyndns.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Bad Filter Set?
Date: Wed, 13 Nov 2002 01:31:11 +0100 [thread overview]
Message-ID: <3DD19D4F.8050703@fugmann.dhs.org> (raw)
In-Reply-To: Pine.LNX.4.44.0211121629140.19945-100000@shortcircuit.dyndns.org
Dan Egli wrote:
> Ok. This is true, so let me clarify. the INTERNAL net should have access
> to all those. The EXTERNAL side needs:
> SMTP, FTP, TELNET, SSH, 4000 & 5000
Ok. I have modified the sctipt to accomodate this.
--------------------------------
# Set default policies.
iptables -P INPUT DROP
iptables -P OUTPUT ACCEPT
iptables -P FORWARD DROP
# Flush all tables.
iptables -F INPUT
iptables -F OUTPUT
iptables -F FORWARD
iptables -t NAT -F PREROUTING
iptables -t NAT -F POSTROUTING
iptables -t NAT -F OUTPUT
iptables -A INPUT -p tcp -m multiport --dports \
smtp,ftp,telnet,ssh,4000,5000
iptables -A INPUT -p tcp -i eth0 -m multiport --dports \
telnet,domain,nntp,ntp,printer,pop3,imap,http,https \
-j ACCEPT
iptables -A INPUT -p udp -i eth0 -m multiport --dports \
domain,ntp,route -j ACCEPT
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A INPUT -j LOG
iptables -A FORWARD -i eth0 -j ACCEPT
iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -j LOG
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5000 \
-j DNAT --to-destination 192.168.0.5:5000
iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to-source 64.122.31.38
echo 1 > /proc/sys/net/ipv4/ip_forward
-------------------------
Regards
Anders Fugmann
prev parent reply other threads:[~2002-11-13 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 17:05 Bad Filter Set? Dan Egli
2002-11-09 14:41 ` Antony Stone
2002-11-09 16:43 ` Dan Egli
2002-11-09 17:29 ` Antony Stone
2002-11-11 6:20 ` Dan Egli
2002-11-11 13:35 ` Anders Fugmann
2002-11-12 23:31 ` Dan Egli
2002-11-13 0:31 ` Anders Fugmann [this message]
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=3DD19D4F.8050703@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=dan@shortcircuit.dyndns.org \
--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