translator
1,001
edits
Difference between revisions of "Firewalls"
m
Template inserted
m (Template inserted) |
m (Template inserted) |
||
| Line 40: | Line 40: | ||
Logging: on (low) | Logging: on (low) | ||
Default: deny (incoming), allow (outgoing), disabled (routed) | Default: deny (incoming), allow (outgoing), disabled (routed) | ||
New profiles: skip</pre>}} | New profiles: skip</pre> | ||
}} | |||
<!--T:11--> | <!--T:11--> | ||
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: | ||
{{UserCmd|command=sudo ufw allow ssh}} | {{UserCmd|command=sudo ufw allow ssh}} | ||
<!--T:12--> | <!--T:12--> | ||
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: | ||
{{UserCmd|command=sudo ufw allow in 8443/tcp}} | {{UserCmd|command=sudo ufw allow in 8443/tcp}} | ||
<!--T:13--> | <!--T:13--> | ||