Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Install pfsense in virtualbox

    Virtualization
    5
    8
    18.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      reneed
      last edited by

      Hi,

      I installed pfsense in virtualbox vm and all the installation process was succesfull,

      But now my problem is when i tried to take the pfsense web interface in web browser getting error to load.

      I know this we need to create bridge in between the guest and host machine.

      I created this and tried to ping the host ip from vm,but its not pinging.showing the error i given below

      "ping : send to: no buffer space availabale"

      Anyone please help me and it would be appreciated.

      Thanks in advance
      Reneed

      1 Reply Last reply Reply Quote 0
      • D
        dcrnac
        last edited by

        I think it would be easier to ping VM from your host.

        Put a fixed ip on PFSense LAN interface, if you set it right you should have a reply, if not,
        bridge another VM's adapter and try again.

        This is very basic stuff, Youtube is your friend.

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          Also, there is no way anyone can help you without any information.  What is your local network?  What do you have for pfSense WAN and LAN IP address, netmask and gateway?

          1 Reply Last reply Reply Quote 0
          • R
            reneed
            last edited by

            these are my local network interface,

            br0: flags=4163<up,broadcast,running,multicast>  mtu 1500
                    inet 192.168.1.58  netmask 255.255.255.0  broadcast 192.168.1.255
                    inet6 fe80::7827:abff:fe39:ffb9  prefixlen 64  scopeid 0x20
                    ether 7a:27:ab:39:ff:b9  txqueuelen 0  (Ethernet)
                    RX packets 0  bytes 0 (0.0 B)
                    RX errors 0  dropped 0  overruns 0  frame 0
                    TX packets 4312  bytes 324453 (316.8 KiB)
                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

            enp3s0: flags=4163<up,broadcast,running,multicast>  mtu 1500
                    inet 192.168.1.58  netmask 255.255.255.0  broadcast 192.168.1.255
                    inet6 fe80::7627:eaff:fe4d:a384  prefixlen 64  scopeid 0x20
                    ether 74:27:ea:4d:a3:84  txqueuelen 1000  (Ethernet)
                    RX packets 260448  bytes 208092416 (198.4 MiB)
                    RX errors 0  dropped 0  overruns 0  frame 0
                    TX packets 186493  bytes 20970917 (19.9 MiB)
                    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

            and for pfsense
            WAN inet  10.0.2.15 and broadcast 10.0.2.255

            LAN inet  192.168.1.59 and broadcast 192.168.1.255

            but one strange thing i can ping google and netconnection is available inside the vm but vm to host ping is still problem.

            After that i tried to down the lan and ping the host,then its succesfull,how is this happened?
            please help if you get maximum information.

            Thanks
            Reneed</up,broadcast,running,multicast></up,broadcast,running,multicast>

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              What is your goal here, just to play with pfSense or are you trying to get it configured as your day-to-day firewall?  What mode are your Virtualbox NICs in?  You should have one bridged NIC for WAN and then one or more intnets for LAN.

              I have set up test labs for pfSense under a variety of virtualization platforms.  For Virtualbox, I create a FreeBSD VM with one bridged NIC and one internet network (intnet1).  If you also want a DMZ, create another NIC on intnet2.  Then you create a lightweight client VM, like Lubuntu, and put its NIC on the same internal network as your pfSense LAN.  Then use the VM client to access pfSense WebGUI.  It just works.  You can even create port-forwards and host virtual servers in your DMZ that you can directly access from your desktop PC.

              1 Reply Last reply Reply Quote 0
              • D
                ditrone
                last edited by

                @KOM:

                What is your goal here, just to play with pfSense or are you trying to get it configured as your day-to-day firewall?  What mode are your Virtualbox NICs in?  You should have one bridged NIC for WAN and then one or more intnets for LAN.

                I have set up test labs for pfSense under a variety of virtualization platforms.  For Virtualbox, I create a FreeBSD VM with one bridged NIC and one internet network (intnet1).  If you also want a DMZ, create another NIC on intnet2.  Then you create a lightweight client VM, like Lubuntu, and put its NIC on the same internal network as your pfSense LAN.  Then use the VM client to access pfSense WebGUI.  It just works.  You can even create port-forwards and host virtual servers in your DMZ that you can directly access from your desktop PC.

                Awesome, i'm setting up a lab like this today (right now).  I'd like to try to use pfsense/virtualbox in production similarly .  Running two pfsense vm's.  The goal being to firewall between our lans and two seperate groups of internet facing servers and to save our electric bill.  My main concern is the resources VB eats up.  The bridged nic's though, does that create any sort of security concern? I'll run debian on my host machine and i'm afraid  if one pfsense vm gets compromised will the others be vunerable because they are sharing eth hardware.  I can lock down the linux machine and it sits behind a dedicated pf box on it's own dedicated switch but due to inexperience i cannot say for certain my pfsense machines are secure.  1 nic per vm necessary?

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  The bridged nic's though, does that create any sort of security concern?

                  Bridged NIC just means it connects directly to the wire instead of using your system as a NAT.

                  In today's world of the NSA, FSB and Chinese spies, I can guarantee none of your servers are secure.  I run pfSense as our border firewall/router on VMware ESXi.  While not impossible, it will be quite difficult to hop from one VM to another unless you manage to exploit some really tasty bug.  Bare-metal hypervisors are trimmed down and present a fairly small attack surface.

                  1 nic per vm necessary?

                  For what, pfSense?  I would say two at the minimum.  I have seen people talk about single-NIC configs for pfSense but I can't imagine why you would do that.

                  1 Reply Last reply Reply Quote 0
                  • S
                    Supermule Banned
                    last edited by

                    If you run it in a VM, then settle your management network on a seperate physical NIC.

                    And dont run the latest and greatest. Wait for updates and error reports.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post