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

    PfSense Gateway VM, Internal VMs unable to reach internet.

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 1 Posters 2.1k Views
    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.
    • N Offline
      Nebulocity
      last edited by

      Hello.  I've been searching these forums and Google for about four hours now, and so far I've had no luck with discovering a resolution to my problem.  I hope that someone here can help.
      I am trying to set up a test network at home for various purposes, which is how I discovered pfSense.  I just started using Knoppix (my first *nix OS), so this is just a tad bit foreign to me.

      I first heard about pfSense on this site: http://rustypainter.com/2012/02/how-to-create-a-windows-server-2008-virtual-lab-using-virtualbox/
      I configured everything, and it worked perfectly.  Both of my VMs (domain controller and web server) were able to connect to the internet.

      Setup:
      Host: Windows 7 Professional x64.
      Virtual Software: VirtualBox
      VM1: PFSense (2 network adapters: adapter1 = Bridged with host, adapter2 = internal network).
      VM2: Windows 2008 R2 Standard Full x64. (Domain Controller, DNS, DHCP)
      VM3: Windows 2008 R2 Standard Full x64. (Web/Application Server)

      Network Setup:
      ISP (Cox Cable Modem) => Linksys WRT54GS2 Router (with DHCP) => PC => pfSense VM => VM Internal Network (2x W2k8R2 VMs)
      VM1:  WAN = DHCP
                LAN = 10.0.0.254/24
      VM2:  10.0.0.11/24
      VM3:  10.0.0.12/24

      Page 3 (http://rustypainter.com/2012/02/how-to-create-a-windows-server-2008-virtual-lab-using-virtualbox/3/) shows that Adapter 1 is set up as a Bridged Network, and Adapter 2 is attached to the Internal network.  The domain controller (VM2) has 10.0.0.254 set as the gateway (pfSense)

      Today though, I am unable to connect to the internet.  Within my internal network, my VMs can ping each other and can ping the pfSense VM.  They are unable to ping my host (192.138.1.101) or Google.com, etc.
      I tried to run through "assigning interfaces" again, and then "set interface(s) IP address", but nothing worked.  The WAN (em0) IP was set to "NONE (DHCP)".

      On my host system, I was unable to ping pfSense…it had no IP, so I went into my router to look at the DHCP lease tables and it wasn't listed there either.  So I went into menu 2 again ("set interface(s) IP address") and gave the WAN (em0) adapter an IP address of 192.138.1.110, to test and see if it would work, and the IP was within the lease range on my router (starts at .100, ends at .150).  I'm was unable to get to the web gui for pfSense at this point also, so I'm not really sure on what I need to do at this point.

      I've not had any luck with it so far, so I'm not sure what the problem is.  The internal network is fine (the VMs can all talk to each other), but anything behind the pfSense VM cannot get outside to the internet.  This leads me to believe that the problem lies with the pfSense VM getting an IP address on my home network (from the router)...but I'm not quite sure how to do it.

      Could someone please help me?  Thanks in advance!

      log.PNG
      log.PNG_thumb
      log.PNG
      log.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • N Offline
        Nebulocity
        last edited by

        More screenshots for troubleshooting (sorry for double post, 300kb attachment limit).

        pfSense-Adapter1.PNG
        pfSense-Adapter1.PNG_thumb
        pfSense-Adapter2.PNG
        pfSense-Adapter2.PNG_thumb
        DC1-Adapter.PNG
        DC1-Adapter.PNG_thumb

        1 Reply Last reply Reply Quote 0
        • N Offline
          Nebulocity
          last edited by

          Aaaaaand last one (domain controller VM network configuration).

          DC-netconfig.PNG
          DC-netconfig.PNG_thumb

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.