UFW, or Uncomplicated Firewall,it’s an interface to iptables , which simplifies the process of configuring a firewall.It’s an difficulty for the beginners to learn how to use it to properly configure a firewall.Because iptables is a solid and flexible tool If you’re looking to get started securing your network, and you’re not sure which tool to use, UFW may be the right choice for you.
This tutorial will help you to set up a firewall with UFW on Ubuntu 16.04.
Step 1 — Using IPv6 with UFW (Optional)
This tutorial is written with IPv4 in mind, but will work for IPv6 as well as long as you enable it.If the Ubuntu server you have is enabled with IPv6 then ensure that UFW is configured to support IPv6 so that it will manage firewall rules for IPv6 in addition to IPv4. To do this, open the UFW configuration with nano or your favorite editor.
sudo nano /etc/default/ufw
Then make sure the value of IPV6 is yes. It should look like this:
Save and close the file now and when the UFW is enabled, it will be configured to write both IPv4 and IPv6 firewall rules.We want to insure that the firewall is configured to allow you to connect via SSH,before enabling UFW.Let’s start with setting the default policies.
Step 2 — Setting Up Default Policies
There’s a rule,if you are getting started to your firewall and that is your default policies. These rules control how to handle traffic that does not explicitly match any other rules. By default, UFW is set to deny all incoming connections and allow all outgoing connections. This means anyone trying to reach your cloud server would not be able to connect, while any application within the server would be able to reach the outside world.
Let’s set your UFW rules back to the defaults so we can be sure that you’ll be able to follow along with this tutorial. To set the defaults used by UFW, use these commands:
- sudo ufw default deny incoming
- sudo ufw default allow outgoing
These commands set the defaults to deny incoming and allow outgoing connections. These firewall defaults alone might suffice for a personal computer, but servers typically need to respond to incoming requests from outside users. We’ll look into that next.
Step 3 — Allowing SSH Connections
If we enabled our UFW firewall now, it would deny all incoming connections. This means that we will need to create rules that explicitly allow legitimate incoming connections — SSH or HTTP connections, for example — if we want our server to respond to those types of requests. If you’re using a cloud server, you will probably want to allow incoming SSH connections so you can connect to and manage your server.
To configure your server to allow incoming SSH connections, you can use this command:
- sudo ufw allow ssh
This will create firewall rules that will allow all connections on port 22, which is the port that the SSH daemon listens on by default. UFW knows what SSH and a number of other service names mean because they’re listed as services in the /etc/services file.
However, we can actually write the equivalent rule by specifying the port instead of the service name. For example, this command works the same as the one above:
- sudo ufw allow 22
If you configured your SSH daemon to use a different port, you will have to specify the appropriate port. For example, if your SSH server is listening on port 2222, you can use this command to allow connections on that port:
- sudo ufw allow 2222
Now that your firewall is configured to allow incoming SSH connections, we can enable it.
Step 4 — Enabling UFW
To enable UFW, use this command:
- sudo ufw enable
You will receive a warning that says the command may disrupt existing SSH connections. We already set up a firewall rule that allows SSH connections, so it should be fine to continue. Respond to the prompt with y.
The firewall is now active. Feel free to run the sudo ufw status verbose command to see the rules that are set. The rest of this tutorial covers how to use UFW in more detail, like allowing or denying different kinds of connections.
Step 5 — Allowing Other Connections
At this point, you should allow all of the other connections that your server needs to respond to. The connections that you should allow depends your specific needs. Luckily, you already know how to write rules that allow connections based on a service name or port; we already did this for SSH on port 22. You can also do this for:
- HTTP on port 80, which is what unencrypted web servers use, using sudo ufw allow http or sudo ufw allow 80
- HTTPS on port 443, which is what encrypted web servers use, using sudo ufw allow https or sudo ufw allow 443
- FTP on port 21, which is used for unencrypted file transfers (which you probably shouldn’t use anyway), using sudo ufw allow ftp or sudo ufw allow 21/tcp
There are several others ways to allow other connections, aside from specifying a port or known service.
Specific Port Ranges
You can specify port ranges with UFW. Some applications use multiple ports, instead of a single port.
For example, to allow X11 connections, which use ports 6000–6007, use these commands:
- sudo ufw allow 6000:6007/tcp
- sudo ufw allow 6000:6007/udp
When specifying port ranges with UFW, you must specify the protocol (tcp or udp) that the rules should apply to. We haven’t mentioned this before because not specifying the protocol simply allows both protocols, which is OK in most cases.
Specific IP Addresses
When working with UFW, you can also specify IP addresses. For example, if you want to allow connections from a specific IP address, such as a work or home IP address of 126.96.36.199, you need to specify from, then the IP address:
- sudo ufw allow from 188.8.131.52
You can also specify a specific port that the IP address is allowed to connect to by adding to any portfollowed by the port number. For example, If you want to allow 184.108.40.206 to connect to port 22 (SSH), use this command:
- sudo ufw allow from 220.127.116.11 to any port 22
If you want to allow a subnet of IP addresses, you can do so using CIDR notation to specify a netmask. For example, if you want to allow all of the IP addresses ranging from 18.104.22.168 to 22.214.171.124 you could use this command:
- sudo ufw allow from 126.96.36.199/24
Likewise, you may also specify the destination port that the subnet 188.8.131.52/24 is allowed to connect to. Again, we’ll use port 22 (SSH) as an example:
- sudo ufw allow from 184.108.40.206/24 to any port 22
Connections to a Specific Network Interface
If you want to create a firewall rule that only applies to a specific network interface, you can do so by specifying “allow in on” followed by the name of the network interface.
You may want to look up your network interfaces before continuing. To do so, use this command:
- ip addr
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
The highlighted output indicates the network interface names. They are typically named something like eth0 or eth1.
So, if your server has a public network interface called eth0, you could allow HTTP traffic (port 80) to it with this command:
- sudo ufw allow in on eth0 to any port 80
Doing so would allow your server to receive HTTP requests from the public Internet.
Or, if you want your MySQL database server (port 3306) to listen for connections on the private network interface eth1, for example, you could use this command:
- sudo ufw allow in on eth1 to any port 3306
This would allow other servers on your private network to connect to your MySQL database.
Step 6 — Denying Connections
If you haven’t changed the default policy for incoming connections, UFW is configured to deny all incoming connections. Generally, this simplifies the process of creating a secure firewall policy by requiring you to create rules that explicitly allow specific ports and IP addresses through.
However, sometimes you will want to deny specific connections based on the source IP address or subnet, perhaps because you know that your server is being attacked from th
Or if you want to deny all connections from 220.127.116.11 you could use this command:
- sudo ufw deny from 18.104.22.168
Now let’s take a look at how to delete rules.
ere. Also, if you want change your default incoming policy to allow (which isn’t recommended in the interest of security), you would need to create deny rules for any services or IP addresses that you don’t want to allow connections for.
To write deny rules, you can use the commands described above, replacing allow with deny.
For example, to deny HTTP connections, you could use this command:
- sudo ufw deny http
Step 7 — Deleting Rules
Knowing how to delete firewall rules is just as important as knowing how to create them. There are two different ways specify which rules to delete: by rule number or by the actual rule (similar to how the rules were specified when they were created). We’ll start with the delete by rule number method because it is easier, compared to writing the actual rules to delete, if you’re new to UFW.
By Rule Number
If you’re using the rule number to delete firewall rules, the first thing you’ll want to do is get a list of your firewall rules. The UFW status command has an option to display numbers next to each rule, as demonstrated here:
- sudo ufw status numbered
To Action From
— —— —-
[ 1] 22 ALLOW IN 22.214.171.124/24
[ 2] 80 ALLOW IN Anywhere
If we decide that we want to delete rule 2, the one that allows port 80 (HTTP) connections, we can specify it in a UFW delete command like this:
- sudo ufw delete 2
This would show a confirmation prompt then delete rule 2, which allows HTTP connections. Note that if you have IPv6 enabled, you would want to delete the corresponding IPv6 rule as well.
By Actual Rule
The alternative to rule numbers is to specify the actual rule to delete. For example, if you want to remove the allow http rule, you could write it like this:
- sudo ufw delete allow http
You could also specify the rule by allow 80, instead of by service name:
- sudo ufw delete allow 80
This method will delete both IPv4 and IPv6 rules, if they exist.
Step 8 — Checking UFW Status and Rules
At any time, you can check the status of UFW with this command:
- sudo ufw status verbose
If UFW is disabled, which it is by default, you’ll see something like this:
If UFW is active, which it should be if you followed Step 3, the output will say that it’s active and it will list any rules that are set. For example, if the firewall is set to allow SSH (port 22) connections from anywhere, the output might look something like this:
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip
To Action From
— —— —-
22/tcp ALLOW IN Anywhere
Use the status command if you want to check how UFW has configured the firewall.
Step 9 — Disabling or Resetting UFW (optional)
If you decide you don’t want to use UFW, you can disable it with this command:
- sudo ufw disable
Any rules that you created with UFW will no longer be active. You can always run sudo ufw enable if you need to activate it later.
If you already have UFW rules configured but you decide that you want to start over, you can use the reset command:
- sudo ufw reset
This will disable UFW and delete any rules that were previously defined. Keep in mind that the default policies won’t change to their original settings, if you modified them at any point. This should give you a fresh start with UFW.
Your firewall should now be configured to allow (at least) SSH connections. Be sure to allow any other incoming connections that your server, while limiting any unnecessary connections, so your server will be functional and secure.