From: Eial Czerwacki <eial@cs.bgu.ac.il>
To: mouss <mouss@netoyen.net>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables block samba or not?
Date: Fri, 25 Jan 2008 16:27:59 +0200 (IST) [thread overview]
Message-ID: <200801251427.m0PERxpJ001193@indigo.cs.bgu.ac.il> (raw)
In-Reply-To: <4799E744.90305@netoyen.net>
the general rules has been changed abit, here:
#!/bin/bash
#PlasmaWall rules
NET_IPS="132.72.144.0/20 192.168.114.0/24"
#setup defaults
echo " - Flushing rules..."
iptables -F
echo " - Setting default policy..."
iptables -P INPUT DROP
iptables -P OUTPUT ACCEPT
iptables -P FORWARD DROP
echo " - Setting input rules..."
# accept all from localhost
/sbin/iptables -A INPUT -s 127.0.0.1 -j ACCEPT
# accept all previously established connections
/sbin/iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
#input
# ssh
#/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT
# ftp / webserver related
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 21 -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 443 -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
# Windows / Samba
for host in $NET_IPS; do
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 135 -s $host -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 139 -s $host -j ACCEPT
/sbin/iptables -A INPUT -p udp -m state --state NEW --dport 137 -s $host -j ACCEPT
/sbin/iptables -A INPUT -p udp -m state --state NEW --dport 138 -s $host -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 426 -s $host -j ACCEPT
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 445 -s $host -j ACCEPT
done
# up to 5 Bit-torrent connections
/sbin/iptables -A INPUT -p tcp -m state --state NEW --dport 6881:6886 -j ACCEPT
#flood defence
#-N syn-flood
#/sbin/iptables -A INPUT -p tcp --syn -j syn-flood
#/sbin/iptables -A syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN
#/sbin/iptables -A syn-flood -j DROP
# Handle fragment flood attacks
/sbin/iptables -A INPUT -f -j LOG --log-prefix "IPTABLES FRAGMENTS: "
/sbin/iptables -A INPUT -f -j DROP
#else
/sbin/iptables -A INPUT -j LOG --log-prefix "Rejected: "
/sbin/iptables -A INPUT -j REJECT --reject-with icmp-port-unreachable
echo " - Setting output rules..."
#output
# accept all previously established connections
/sbin/iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
/sbin/iptables -A OUTPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT
echo " done."
On Fri 25 Jan 15:42 2008 mouss wrote:
> Eial Czerwacki wrote:
> > ok, I've deiced to give it a try, after adding the line, I can browse the local network, e.g. samba isnt blocked again.
> > you guys say that this isnt the problem, now, after enabling it, is there any threat to my system?
> >
>
> you mean enabled an output rule and it worked? now, I'm puzzled. post
> the full config.
>
> and no, allowing output should not be a problem.
> -
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-01-25 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 22:33 iptables block samba or not? Eial Czerwacki
2008-01-22 1:52 ` Leonardo Rodrigues Magalhães
2008-01-23 22:00 ` Dzianis Kahanovich
2008-01-24 20:16 ` mouss
2008-01-24 20:17 ` Eial Czerwacki
2008-01-24 21:13 ` mouss
2008-01-24 21:37 ` Martijn Lievaart
2008-01-25 10:40 ` Eial Czerwacki
2008-01-25 11:49 ` mouss
2008-01-25 13:35 ` Eial Czerwacki
2008-01-25 13:42 ` mouss
2008-01-25 14:27 ` Eial Czerwacki [this message]
2008-01-25 15:15 ` mouss
2008-01-25 16:02 ` Eial Czerwacki
2008-01-25 16:13 ` mouss
2008-01-25 16:53 ` Eial Czerwacki
2008-01-25 19:02 ` Martijn Lievaart
2008-01-25 16:04 ` Steven Ayre
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=200801251427.m0PERxpJ001193@indigo.cs.bgu.ac.il \
--to=eial@cs.bgu.ac.il \
--cc=mouss@netoyen.net \
--cc=netfilter@vger.kernel.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