From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rob Sterenborg" Subject: RE: REJECT target not as policy Date: Mon, 20 Aug 2007 21:11:53 +0200 Message-ID: <000801c7e35d$f7d39210$0101000a@tanjian> References: <20070820135206.GA18644@bart.bertram-scharpf.homelinux.com> <200708201608.39032.r.laban@ism.nl> <46C9B8A2.5040201@plouf.fr.eu.org><20070820174642.GA22613@bart.bertram-scharpf.homelinux.com> <46C9E0E4.2080200@plouf.fr.eu.org> Return-path: In-Reply-To: <46C9E0E4.2080200@plouf.fr.eu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: netfilter@lists.netfilter.org >> On an other list I was told it were a good idea to set >> REJECT as policy. > > I could be a good idea if it was possible. Maybe the person who told > you mixed up iptables and ipchains, its "predecessor" for 2.2 > kernels. IIRC ipchains allowed REJECT as a policy. You could emulate a REJECT policy by having this as the very last rules: $ipt -A INPUT -p tcp -j REJECT --reject-with tcp-reset $ipt -A INPUT -j REJECT (I thought it was like this..) But, if you dynamically add rules then you have to take care of at/from which position you insert/delete them.