Linux iptables Firewall Simplified Examples
In the previous post, we talked about how to Secure Linux Server Using Hardening Best Practices. Some people asked me about the firewall section, which was a brief introduction to the iptables firewall. Today we will discuss in detail the Linux iptables firewall and how to secure your server traffic using that awesome firewall.
Table of Contents
Iptables on CentOS 7
If you are using CentOS 7, you will find that firewalld manages iptables, so if you want to go back to iptables, you have to stop and mask firewalld.
$ systemctl stop firewalld $ systemctl mask firewalld
Then install iptables service and enable it:
$ yum install iptables-services $ systemctl enable iptables
Then you can start it:
$ systemctl start iptables
How Linux firewall works
Iptables firewall functions are built on the Netfilter framework that is available in the Linux kernel for packets filtering.
There are two types of firewalls:
Stateless firewall process each packet on its own, it means it doesn’t see other packets of the same connection.
Stateful firewall this type of firewall cares about all packets passed through it, so it knows the state of the connection. It gives more control over the traffic.
Netfilter contains tables. These tables contain chains, and chains contain individual rules.
If a packet matches any rule, the iptables will apply the rule action to that packet.
The actions can be: accept, reject, ignore, or pass the packet on to other rules for more processing.
Netfilter can process incoming or outgoing traffic using the IP address and port number.
The iptables command manages and configures Netfilter.
Before we start writing firewall commands, we need to understand the firewall structure a bit so we can write firewall rules easily.
iptables firewall tables
Netfilter has three tables that can carry rules for processing.
The iptables filter table is the main table for processing the traffic.
The second is the nat table, which handles NAT rules.
The third table is the mangle table for mangling packets.
Each table of the tables mentioned above contains chains; these chains are the container of the rules of iptables.
The filter table contains FORWARD, INPUT, and OUTPUT chains. You can create a custom chain to save your rules on it.
If a packet is coming to the host, iptables will process it by INPUT chain rules.
If the packet is going to another host, that means OUTPUT chain rules will process it.
The iptables uses the FORWARD chain for handling packets that have accessed the host but are destined to another host.
Each chain in the filter table has a policy. The policy is the default action that iptables take.
The policy could be DROP, REJECT, and ACCEPT.
The ACCEPT policy allows the packets to pass the firewall. The DROP policy drops a packet without informing the client. The REJECT policy also drops the packet and informs the sender.
From a security perspective, you should drop all the packets coming to the host and accept only the packets that come from trusted sources.
Adding iptables rules
You can add a new rule using the iptables command like this:
$ iptables -A INPUT -i eth1 -p tcp --dport 80 -d 220.127.116.11 -j ACCEPT
Let’s break this command into pieces so we can understand everything about it.
The -A means we are adding a new rule. By default, iptables adds all new rules to the filter table unless you specify another table.
The -i flag specifies the device that will apply the rule to. If you don’t specify a device, iptables will apply the rule to all incoming traffic regardless of the devices.
The -p flag specifies the packet’s protocol that you want to process, which is TCP in our case.
The –dport flag specifies the destination port, which is 80.
The -d specifies the destination IP address, which is 18.104.22.168. If no destination IP address specified, the rule would apply to all incoming traffic on eth1 regardless of IP address.
The -j specifies the action or the JUMP action to do. Here we are accepting the packets using the accept policy.
The above rule allows incoming HTTP traffic, which is on port 80.
What about allowing outgoing traffic?
$ iptables -A OUTPUT -o eth1 -p tcp --sport 80 -j ACCEPT
You can use the -A flag to add rules to the OUTPUT chain.
The -o flag is used for the device used for outgoing traffic.
The -sport flag specifies the source port.
You can use the service name like http or https instead of the numeric port number on sport or dport. All services names are in /etc/services file.
You should use the service name rather than a port number, which makes reading rules easier.
iptables rules order
The iptables places new rules at the end of the chain. You can add it to the top by using -I option.
The sequence of the rules matters as you will see now. You can insert your rules exactly where you want using the I flag.
Look at the following rules to understand how rules ordering matters:
$ iptables -I INPUT 3 -i eth1 -p udp -j ACCEPT $ iptables -I INPUT 4 -i eth1 -p udp --dport 80 -j DROP
The first rule accepts all UDP traffic comes to eth1, and the number 3 is the rule order.
The second rule drops the traffic that enters port 80.
The first rule will accept all the traffic, then the second rule which should drop the traffic will do nothing since iptables passes the traffic in the first rule.
Your rules should make sense since the order of the rules in the chain matters.
List iptables rules
You can list the rules in a chain using -L flag:
$ iptables -L INPUT
You can show the line numbers for rules using –line-numbers:
$ iptables -L INPUT --line-numbers
The list shows the names of the services. You can show port numbers instead using -n option:
$ iptables -L INPUT -n --line-numbers
The above rule will make the listing faster because it prevents iptables from DNS resolution and service lookups.
You can list all rules for all chains like this:
$ iptables -L -n --line-numbers
To get how many packets processed by each rule, you can use the -v flag:
$ iptables -L -v
Also, you can reset the counters to zero using -Z flag.
Now we can add a new rule to any chain we want, we can insert the rule in a specific order, and we can list the rules for any chain or all chains, but what about deleting a rule?
You can delete a rule using -D flag:
$ iptables -D INPUT -i eth1 -p tcp --dport 80 -d 22.214.171.124 -j ACCEPT
This command will delete the HTTP rule that you specified earlier.
Before you delete a rule, just make sure of the rule specification by listing it, then delete it.
You can delete the rule using the order number instead of writing the rule specifications.
$ iptables -D INPUT 2
You can delete all rules in a specific chain using -F flag, which means flush all rules.
$ iptables -F INPUT
If you forget to mention the chain name when using -F flag, then all chain rules will be deleted.
You can replace existing rules with your own rule using -R flag:
$ iptables -R INPUT 1 -i eth1 -p tcp --dport httpht -d 126.96.36.199 -j ACCEPT
This command will replace the first rule in the INPUT chain with the typed rule.
Listing Specific Table
To list a specific table, use the -t flag with the table name like this:
$ iptables -L -t nat
Here we list the rules in the nat table.
Iptables User Defined Chain
To create a user-defined chain, use the -N flag.
$ iptables -N MY_CHAIN
Also, you can rename it using -E flag.
$ iptables -E MY_CHAIN NEW_NAME
And you can delete the user-defined chain using -X flag.
$ iptables -X MY_CHAIN
If you don’t mention the chain name when using -X flag, it will delete all user-defined chains. You can’t delete built-in chains like INPUT and OUTPUT.
Redirection to a User Defined Chain
You can redirect packets to a user-defined chain like built-in chains using -j flag.
$ iptables -A INPUT -p icmp -j MY_CHAIN
The above rule will redirect all ICMP traffic to the chain MY_CHAIN.
Setting The Default Policy for Chains
You can use the -P flag to set the default policy for a specific chain. The default policy could be ACCEPT, REJECT, and DROP.
$ iptables -P INPUT DROP
So now, the input chain will drop any packet come unless you write a rule to allow any incoming traffic.
The attacker sends SYN packets only without completing the TCP handshake and as a result, the receiving host would have many opened connections, and your server becomes too busy to respond to other clients.
We can use the limit module of iptables firewall to protect us from SYN flooding.
$ iptables -A INPUT -i eth1 -p tcp --syn -m limit --limit 10/second -j ACCEPT
Here we specify 10 SYN packets per second only. You can adjust this value according to your network needs.
If this will throttle your network, you can use SYN cookies.
file and add this line:
net.ipv4.tcp_syncookies = 1
Then save and reload.
$ sysctl -p
Drop INVALID State Packets
The INVALID state packets are packets that don’t belong to any connection and you drop them.
$ iptables -A INPUT -m state --state INVALID -j DROP
This rule will drop all incoming invalid state packets.
Drop Fragmented Packets
Fragmented packets are broken pieces of large malformed packets, and you should write rules to drop them.
The -f flag tells the iptables firewall to select all fragments. So if you are not using iptables as a router, you can drop fragmented packets.
$ iptables -A INPUT -f -j DROP
Save iptables Rules
If you reboot your server, you will lose all rules you wrote, so how to persist them?
You can save all of your rules using the iptables-save command if you are using CentOS or Red Hat.
iptables-save > /etc/sysconfig/iptables
On CentOS 7, you can save rules like this:
$ service iptables save
You can save specific table like filter table only:
$ iptables-save -t filter
Also, you can use iptables-restore to restore rules.
On Debian based distros, you can use the iptables-persistent package to save and restore rules.
First, install it:
$ apt-get install iptables-persistent
Then you can save and restore rules:
$ netfilter-persistent save
$ netfilter-persistent reload
For further reading, you can check the official docs from here:
I hope you find the iptables firewall easy. Keep coming back.
Mokhtar is the founder of LikeGeeks.com. He works as a Linux system administrator since 2010. He is responsible for maintaining, securing, and troubleshooting Linux servers for multiple clients around the world. He loves writing shell and Python scripts to automate his work.
6 thoughts on “Linux iptables Firewall Simplified Examples”
Thanks a lot.
Where to safe the iptables rules under Ubuntu/Debian?
You can use iptables-persistent package
First, install it:
$ apt-get install iptables-persistent
Then you can save rules like this
$ netfilter-persistent save
Sorry for sounding harsh.
But as soon as I see the combination of “firewall” and “simplified” I switch to alert mode.
The fact that ip6tables is not even mentioned makes me expect the worse.
Let me make it very clear for all: You firewall is your first line of defence.
There is NO SIMPLIFICATION.
Trying to do so gives people a false sense of security.
If this is not something you dived deep into it: HANDS OFF!
ANY talk about firewall should start with referring to: http://www.netfilter.org/ , http://lartc.org/ ,
And should never be focussed on your favourite distribution.
Why? because security is TOO important. Working for over 20 years with Linux learned me that much.
Thanks for your comment. The simplification I meant here is about writing iptables in a simple way.
Moreover, the article doesn’t contain any clue about making the machine full secured, it’s just about using iptables.
Regarding referring to netfilter, I already mentioned that iptables is based on netfilter on the article.
Again, I’m talking about iptables firewall nothing more, you can read the other articles about securing Linux and before you argue, there is no complete guide for security.
Finally, I’m not focusing on a specific distribution at all.