7

incoming ACCEPT all iptables rule still appearing

view full story
linux-howto

http://unix.stackexchange.com – I'm following this guide here: http://isalazyadmin.net/2009/07/02/configuring-a-basic-firewall-for-debi... And I have the iptables listed shown, but my server still appears to be accepting all incoming connections (ie: bittorrent peers are still connecting, even though I didn't allow those ports). /etc/iptables.rules *filter # This will allow all loopback (lo0) traffic and drop all traffic to 127/8 # that does not use lo0 -A INPUT -i lo -j ACCEPT -A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT # This accepts all already established connections -A INPUT -m state --state ESTABLISHED,RELATE (HowTos)

Danial's picture
Submitted by Danial on 01/11/2013 – Made popular on 01/11/2013

Stories similar to incoming ACCEPT all iptables rule still appearing

open Ports in IP tables 3 years 20 weeks ago

Hi I would like to open some port from IN to OUT

pop3,smtp. whenever i tried to add some rules to existing iptables it gives me an error Applying iptables firewall rules: iptables-restore: line 21 failed

I am using the Cent OS 5.3

how do i open the ports?

INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0]

When trying to setup a redirect and save the iptables file via iptables-restore, i get the following error:

iptables-restore v1.4.8: Line 31 seems to have a -t table option.

Error occurred at line: 31

Here's the full file, with the line im trying to use to redirect at #31

*filter

# Allows all loopback (lo0) traffic and drop all traffic to 127/8 that doesn't use lo0 -A INPUT -i lo -j ACCEPT -

Current setup

Centos which is a Web, Mail (Postfix,Dovecot), FTP Server and Gateway with public ip and private ip (for LAN Gateway).

We are planning to implement external firewall box and bring the server to LAN

Please guide on configuring IPTables...

Simple State Firewall 47 weeks 21 hours ago

I just set up my firewall following the wiki, just the basics down to the knocking section.After I restarted my connection Firefox works which is great, although so does Transmission.. This leads me to think maybe my firewall is not working correctly, as the only ports I opened were 80 and 53.

I've setup IPTables with the following script...

When I have send a request to an application running on a machine which following firewall rules are applied, it waits so long. When I have deactivated the iptables rule, it responses immediately.

iptables tcp NEW state 11 weeks 15 hours ago

I am new to iptables and learning them from here

I have questions about the following:

iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT This is the rule that does most of the work, and again we are adding (-A) it to the INPUT chain. Here we're using the -m switch to load a module (state).

I'm setting up a new Centos 5.6 system and can't get my iptables firewall to work correctly. it won't let me use SSH through it. I'm new to Centos but not to Linux or iptables.

I've been removing things until I have isolated the problem. I set up the firewall with a default ACCEPT rule for the INPUT chain. I can connect through to the server fine.

I'm trying to find out why changing my default iptables policy is affecting what nmap sees when it scans my host.

Consider the following iptables setup:

iptables -F iptables -A INPUT -p tcp -s 10.1.0.0/20 --dport 22 -j ACCEPT

iptables -P INPUT ACCEPT iptables -P FORWARD DROP iptables -P OUTPUT ACCEPT

iptables -A INPUT -i lo -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j AC