Difference between revisions of "Firewall Manager/9.2"

From PC-BSD Wiki
Jump to: navigation, search
m
m
Line 1: Line 1:
<noinclude>{{NavHeader|back=Network Configuration|forward=Life Preserver}}</noinclude>
+
<noinclude>{{NavHeader|back=Network Configuration|forward=Bluetooth}}</noinclude>
 
PC-BSD uses the [http://www.openbsd.org/faq/pf/ PF firewall] to protect your system. By default, the firewall is configured to let your system make Internet connections, use the ping utility, and to communicate with other Windows and Unix-like systems using SMB and NFS.
 
PC-BSD uses the [http://www.openbsd.org/faq/pf/ PF firewall] to protect your system. By default, the firewall is configured to let your system make Internet connections, use the ping utility, and to communicate with other Windows and Unix-like systems using SMB and NFS.
  

Revision as of 04:16, 4 February 2012

(Sorry for the inconvenience)

PC-BSD uses the PF firewall to protect your system. By default, the firewall is configured to let your system make Internet connections, use the ping utility, and to communicate with other Windows and Unix-like systems using SMB and NFS.

Advanced users who are already familiar with pf will find the default rulebase in /etc/pf.conf. Users who aren't familiar with directly editing this file can instead use the Firewall Manager GUI utility to view and modify the existing firewall rules.

NOTE: typically it is not necessary to change the firewall rules. You should not remove any existing rules unless you fully understand what the rule does. Similarly, you should only add rules if you understand the security implications of doing so, especially if the rule allows connections to your computer.

To access the Firewall Manager, go to Control Panel -> Firewall Manager and input the administrative password. Figure 7.8a shows the initial screen when you launch this utility:

Figure 7.8a: Firewall Manager Utility

Firewall1.png

The General Settings tab of this utility allows you to:

  • determine whether or not the firewall starts when the system boots; unless you have a reason to do so and understand the security implications, this box should remain checked so that your system is protected by the firewall
  • start, stop, or restart the firewall: if you add, delete, or modify a firewall rule, you should restart the firewall for your changes to take effect
  • restore default configuration: this button allows you to return to the original, working configuration should you not like the changes you make to your firewall rules

To view or modify the firewall rules, click on the Exceptions tab, seen in Figure 7.8b:

Figure 7.8b: Adding a New Firewall Rule

Firewall2b.jpeg

In this example, the user has clicked on the "Add entry" button to add a new firewall rule. The following information is needed when creating a rule:

  • Service or Port: you can either select the name of the service you wish to allow or block from the drop down menu or type in the number of the port used by the service. Which you choose does not matter as the firewall will match the name and number for you and display both after you save the rule.
  • Policy: you need to choose whether to allow or block this service/port.
  • Direction: use the drop down menu to determine whether the policy applies to incoming or outgoing connections; the direction is from the perspective of your computer i.e. do you want others to connect to your service (incoming) or do you want to connect the service running on another system (outgoing).
  • Protocol: use the drop down menu to select whether the service uses the TCP or UDP protocol.
  • Interface: use the drop down menu to select the interface that will make or receive the connection.

Once you have made your selections, press Ok to save the new rule.

NOTE: the new rule will not be used by the firewall until the firewall is restarted. Click the Restart button if you wish to test the rule or start using it immediately.

You should take a moment to test that your new rule(s) work as expected. For example, if you create a rule to allow an SSH connection, try connecting to your PC-BSD system using SSH to verify that the firewall is now allowing the connection.