Installation and Configuration of pfSense 2.3.4 Firewall Router

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Rob Turner

He is an Instructor of Computer Technology with Ball State University where he currently teaches all of the departments Linux courses and co-teaches Cisco networking courses. He is an avid Debian user as well as many of the derivatives of Debian such as Mint, Ubuntu, and Kali. Rob holds a Masters in Information and Communication Sciences as well as several industry certifications from Cisco, EC-Council, and Linux Foundation.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

8 Responses

  1. KEN says:

    Hi! I’m student, I have homework about install PFSense in Centos 6.7 and I would like to “How to configuration of PFsense Fire wall 2.4.1”.

    Can you help me.

  2. nay says:

    I am beginner and I have tested Pfsense 2.3.4 on vbox. Pfsense have 2 NIC’s, one is WAN that is dhcp, other one is LAN is static. I use guest OS on vbox and connect to pfsense. pfsense access internet, but Guest OS didn’t get internet but ping to 8.8.8.8 is ok and ping to http://www.google.com not ok. nslookup show

    default server are not available ; 
    defaault server : unknow ; address:127.0.0.1. 
    

    how should I do that you guide me?

    • Rob Turner says:

      Nay,

      Your nslookup output suggests that your computer doesn’t have a DNS server configured. If you’re doing all of this in VBox, you’ll have to create an internal network for your virtual machine and the PFsense VM. This will allow the pfsense box to hand out DHCP information on the LAN interface to the virtual guest machine. At that point the guest will use the PFsense box for DNS. So your network would look like this:

      INTERNET ———— EM0(WAN) on Pfsense+++++Internal routing on Pfsense++++++EM1(LAN) on Pfsense ———- Virtual Box Guest (guest and pfsense EM1 on internal virtual box network)

  3. Faruk says:

    Thanks for the tutorial, However I have some questions regarding the configurations?

    I’ve setup Pfsense on VM an cloud and I’ve assigned Public IP to WAN and Local IP like 192.168.3.1/24 to LAN and made this DHCP with a IP range like 192.168.3.10-192.168.3.254.

    1. What rules or NAT should be configured in order the IP addresses received the IPs from DHCP to get out to internet?
    2. How many Gateway is preferred to have and which one should be default?
    3. In what situations should Static Route be configured?

    Hope to hear you soon.
    Thanks in advance,

    • Rob Turner says:

      Faruk,

      1. The NAT rules would depend on your network and what needs to be translated. I can’t really provide any insight there without knowing more about the network.
      2. Most of the time networks only need one gateway. You can configure multiple but the hosts will only be able to use one at a time.
      3. Static route needs would again be dependent on your network setup. Most networks have a default static route out to the ISP and the ISP will generally have a static summary route back to the network. Regardless with PfSense in most home/small business situations, you won’t need to mess with static routes.

  4. evgeny says:

    I have a three-router circuit. Both are linked to IPSEC to the main one. Everyone can see and enter. I’m running open to the main router. VPN client connections only see the main router’s network. I want to see all networks that connect to openvpn.

  5. ehsan hedayati says:

    nice tutorial
    thanks very much!

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *