From: Grant Taylor <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: filtering ruleset help sought
Date: Wed, 17 Aug 2005 00:40:03 -0500 [thread overview]
Message-ID: <4302CDB3.3070706@riverviewtech.net> (raw)
In-Reply-To: <4300FAAD.4060305@ttienterprises.org>
Yesh! That snippet of firewall code is, um, well interesting to say the least if not broken. (I'm very tired if I come off a bit crass.)
To do what you are wanting to do I would attempt something like the following:
iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP
iptables -t filter -P OUTPUT DROP
iptables -t filter -N InternetTraffic
iptables -t filter -A InternetTraffic -d <IP of site 1> -j ACCEPT
iptables -t filter -A InternetTraffic -d <IP of site 2> -j ACCEPT
...
iptables -t filter -A InternetTraffic -d <IP of site n> -j ACCEPT
iptables -t filter -A InternetTraffic -j DROP
iptables -t filter -A INPUT -i eth0 -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT
iptables -t filter -A INPUT -i eth0 -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT
iptables -t filter -A INPUT -i eth1 -j ACCEPT
iptables -t filter -A FORWARD -i eth0 -o eth1 -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT
iptables -t filter -A FORWARD -i eth0 -o eth1 -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT
iptables -t filter -A FORWARD -i eth1 -o eth0 -p tcp --dport 80 -j InternetTraffic
iptables -t filter -A FORWARD -i eth1 -o eth0 -p tcp --dport 443 -j InternetTraffic
iptables -t filter -A OUTPUT -o eth0 -p tcp --dport 80 -j InternetTraffic
iptables -t filter -A OUTPUT -o eth0 -p tcp --dport 443 -j InternetTraffic
iptables -t filter -A OUTPUT -o eth1 -j ACCEPT
One word to the wise. You will likely need to have DNS somewhere for your systems to be able to find the hosts that they want to get to. If said DNS needs to pass through your firewall you will need to update the rules accordingly to allow it.
Grant. . . .
Barry Fawthrop wrote:
> Hi
>
> I was given a iptables ruleset (that I think was generated by firestarter)
> I don't have GUI nor do I want to so I have no means to test it.
> It runs on a gateway machine ETH0 = Wan and ETH1 = LAN NICs
>
> I'm looking for a simple ruleset that will deny all outgoing traffic
> accept to a list of IP addresses found in a file
> and only on port 80 for HTTP access only.
>
> I have this:
>
> $IPT -t filter -A INPUT -s $INNET -d 0/0 -j DROP
> $IPT -t filter -A OUTPUT -s $INNET -d 0/0 -j DROP
> $IPT -t filter -A OUTPUT -p icmp -s $INNET -d 0/0 -j DROP
>
> while read s1 s2
> do
> $IPT -t filter -A INPUT -s $INNET -d $s1 --dport 80 -j ACCEPT
> $IPT -t filter -A OUTPUT -s $INNET -d $s1 --dport 80 -j ACCEPT
> $IPT -t filter -A OUTPUT -p icmp -s $INNET -d $s1 -j ACCEPT
> done < /allowed-hosts
>
> 1) doesn't work complains about --dport
> 2) I can still ping other ip addresses not found in the allowed-hosts file?
>
> Any help, most welcome
> Thank You
> Barry
prev parent reply other threads:[~2005-08-17 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 20:27 filtering ruleset help sought Barry Fawthrop
2005-08-15 20:49 ` John A. Sullivan III
2005-08-15 21:02 ` Barry Fawthrop
2005-08-15 21:22 ` John A. Sullivan III
2005-08-17 5:40 ` Grant Taylor [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=4302CDB3.3070706@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.