8,138
edits
Difference between revisions of "Firewalls/en"
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 5: | Line 5: | ||
Running a local firewall is almost always a good practice. Even when you are behind a network firewall, a local firewall protects you from threats on the inside of your network. | Running a local firewall is almost always a good practice. Even when you are behind a network firewall, a local firewall protects you from threats on the inside of your network. | ||
=UFW= | =UFW= | ||
UFW stands for Uncomplicated FireWall, and is a program for managing a netfilter firewall. It provides a command line interface and aims to be uncomplicated and easy to use. UFW is far simpler than iptables and a good place to start unless you have very specialized needs. | UFW stands for Uncomplicated FireWall, and is a program for managing a netfilter firewall. It provides a command line interface and aims to be uncomplicated and easy to use. UFW is far simpler than iptables and a good place to start unless you have very specialized needs. | ||
==Installing UFW== | ==Installing UFW== | ||
You can install the {{ic|ufw}} package using you favorite package manager or the command: | You can install the {{ic|ufw}} package using you favorite package manager or the command: | ||
pamac install ufw | {{UserCmd|command=pamac install ufw}} | ||
Once UFW is installed you need to start and enable it using the commands: | Once UFW is installed you need to start and enable it using the commands: | ||
sudo systemctl enable ufw.service | {{UserCmd|command=sudo systemctl enable ufw.service}} | ||
sudo ufw enable | {{UserCmd|command=sudo ufw enable}} | ||
{{warning|Don't enable both iptables.service and ufw.service}} | {{warning|Don't enable both iptables.service and ufw.service}} | ||
==Adding Rules== | ==Adding Rules== | ||
To view the current configuration you can use the command {{ic|ufw status}}. Here is what it looks like in a new install: | To view the current configuration you can use the command {{ic|ufw status}}. Here is what it looks like in a new install: | ||
sudo ufw status verbose | {{UserCmdOutput|command=sudo ufw status verbose|result= | ||
Status: active | <pre>Status: active | ||
Logging: on (low) | Logging: on (low) | ||
Default: deny (incoming), allow (outgoing), disabled (routed) | Default: deny (incoming), allow (outgoing), disabled (routed) | ||
New profiles: skip | New profiles: skip</pre> | ||
</pre> | }} | ||
This indicates that it will block all incoming traffic and allow all outgoing traffic. This is a good starting point for most desktop systems. However, often we will want to allow some incoming traffic. This can be done with the command {{ic|ufw allow}}. For example, if we want to allow incoming ssh traffic so we can connect to the machine from other machines on the network we could use the command: | This indicates that it will block all incoming traffic and allow all outgoing traffic. This is a good starting point for most desktop systems. However, often we will want to allow some incoming traffic. This can be done with the command {{ic|ufw allow}}. For example, if we want to allow incoming ssh traffic so we can connect to the machine from other machines on the network we could use the command: | ||
sudo ufw allow ssh | {{UserCmd|command=sudo ufw allow ssh}} | ||
If we wanted to also tcp connections to a local webserver on a non-standard https port, 8443. We could use the command: | If we wanted to also tcp connections to a local webserver on a non-standard https port, 8443. We could use the command: | ||
sudo ufw allow in 8443/tcp | {{UserCmd|command=sudo ufw allow in 8443/tcp}} | ||
{{tip|When you don't specify "in" or "out", "in" is assumed}} | {{tip|When you don't specify "in" or "out", "in" is assumed}} | ||
==UFW and Applications== | ==UFW and Applications== | ||
You may notice a difference in the above two commands. When we built the rules for ssh we used the name and for https we used the port number, 8443. This is because UFW has a small database of applications it knows the ports for. You can see the list with the command: | You may notice a difference in the above two commands. When we built the rules for ssh we used the name and for https we used the port number, 8443. This is because UFW has a small database of applications it knows the ports for. You can see the list with the command: | ||
{{UserCmd|command=sudo ufw app list}} | |||
For applications on the list you can add them by name. If you want to review the configuration for one of the applications, you can use the command {{ic|ufw app info}}. For example, to the configuration for ssh: | |||
{{UserCmdOutput|command=sudo ufw app info SSH|result= | |||
<pre> | <pre>Profile: SSH | ||
Profile: SSH | |||
Title: SSH server | Title: SSH server | ||
Description: SSH server | Description: SSH server | ||
Port: | Port: | ||
22/tcp | 22/tcp</pre> | ||
</pre> | }} | ||
{{tip|When using ufw app the commands are case sensitive but when adding rules they are not}} | {{tip|When using ufw app the commands are case sensitive but when adding rules they are not}} | ||
Some additional preconfigured applications can be added by installing the package {{ic|ufw-extras}} with your favorite package manager or the command: | Some additional preconfigured applications can be added by installing the package {{ic|ufw-extras}} with your favorite package manager or the command: | ||
pamac install ufw-extras | {{UserCmd|command=pamac install ufw-extras}} | ||
==Removing Rules== | ==Removing Rules== | ||
Rules can be removed with the {{ic|ufw delete}} command. For example, to delete our 8443 rules we could use the command: | Rules can be removed with the {{ic|ufw delete}} command. For example, to delete our 8443 rules we could use the command: | ||
sudo ufw delete allow 8443/tcp | {{UserCmd|command=sudo ufw delete allow 8443/tcp}} | ||
You can also delete them by number. This is easier if you have a numbered list which you can see with the command: | You can also delete them by number. This is easier if you have a numbered list which you can see with the command: | ||
{{UserCmdOutput|command=sudo ufw status numbered|result= | |||
<pre>Status: active | |||
To Action From | |||
-- ------ ---- | -- ------ ---- | ||
[ 1] 22 ALLOW IN Anywhere | [ 1] 22 ALLOW IN Anywhere | ||
[ 2] 22 (v6) ALLOW IN Anywhere (v6)</pre> | [ 2] 22 (v6) ALLOW IN Anywhere (v6) | ||
</pre>}} | |||
Now if we wanted to stop allowing ssh on ipv6 we could use the command: | Now if we wanted to stop allowing ssh on ipv6 we could use the command: | ||
sudo ufw delete 2 | {{UserCmd|command=sudo ufw delete 2}} | ||
==GUFW== | ==GUFW== | ||
[[File:gufw.jpg|thumb|left|240px]] | [[File:gufw.jpg|thumb|left|240px]] | ||
Prefer to use GUI applications and still want to manage your firewall? No problem. GUFW is a GTK front-end for UFW that aims to make managing a Linux firewall as accessible and easy as possible. It features pre-sets for common ports and p2p applications. | Prefer to use GUI applications and still want to manage your firewall? No problem. GUFW is a GTK front-end for UFW that aims to make managing a Linux firewall as accessible and easy as possible. It features pre-sets for common ports and p2p applications. | ||
If it is not installed already gufw can be installed from the repos: | If it is not installed already gufw can be installed from the repos: | ||
pamac install gufw | {{UserCmd|command=pamac install gufw}} | ||
It will now be available in the menu as '''Firewall Configuration''' or by running {{ic|gufw}} directly. | It will now be available in the menu as '''Firewall Configuration''' or by running {{ic|gufw}} directly. | ||
<div style="clear: both"></div> | <div style="clear: both"></div> | ||
=iptables= | =iptables= | ||
iptables is included as part of the Linux kernel. iptables is significantly more complicated than using a tool like UFW. As a result, a full tutorial on iptables is beyond the scope of this wiki. Using iptables on Manjaro should be the same for every distribution of Linux so there is plenty of available documentation. Some of this is linked [[Firewalls#See_Also|below]]. Here are some basics to get you started. | iptables is included as part of the Linux kernel. iptables is significantly more complicated than using a tool like UFW. As a result, a full tutorial on iptables is beyond the scope of this wiki. Using iptables on Manjaro should be the same for every distribution of Linux so there is plenty of available documentation. Some of this is linked [[Firewalls#See_Also|below]]. Here are some basics to get you started. | ||
To enable loading rules on startup you can use the command: | To enable loading rules on startup you can use the command: | ||
sudo systemctl enable iptables.service | {{UserCmd|command=sudo systemctl enable iptables.service}} | ||
This will load the rules from the file {{ic|/etc/iptables/iptables.rules}}. | This will load the rules from the file {{ic|/etc/iptables/iptables.rules}}. | ||
To display the currently loaded rules: | To display the currently loaded rules: | ||
sudo iptables -L | {{UserCmd|command=sudo iptables -L}} | ||
To save the current rules to a file | To save the current rules to a file | ||
sudo sh -c "iptables-save > /etc/iptables/iptables.rules" | {{UserCmd|command=sudo sh -c "iptables-save > /etc/iptables/iptables.rules"}} | ||
To load the rules from a file | To load the rules from a file | ||
{{UserCmd|command=sudo sh -c "iptables-restore > /etc/iptables/iptables.rules"}} | |||
To allow ssh connections | To allow ssh connections | ||
sudo iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT | {{UserCmd|command=sudo iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT}} | ||
sudo iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT | {{UserCmd|command=sudo iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT}} | ||
=See Also= | =See Also= | ||