Virtual Box Installation Problems



  • Hello everyone.  I am having a problem running PfSense and am hoping to get some insight.

    My problem stems with these issues:

    I am not able to ping the pfsense VM using my host machine or other virtual machines.

    I am not able to access the administrative console via SSL.

    Here are my network settings:

    Also, pfsense itself is able to ping my host machine and virtual machines, but again, the reverse pings offer 'request timed out'.

    Here is what I am seeing and my WAN/LAN settings within pfsense.

    Any idea why this is happening?  So far, I'm pretty miffed.

    Thank you for any/all help.


  • Netgate Administrator

    By default all traffic will be blocked on WAN. You will not be able to ping or access the webGUI on 10.0.1.105.

    You should be able to access it on LAN. Another VM connected via the 'intnet' internal network should be able ping and access the webGUI.
    Are you using pfSense for DHCP? All static IPs? How are you other VMs connected?

    Steve



  • Stephen, thank you for the reply.

    You gave me some clues for which I did some more testing.  I set a linux distro to intnet and was then able to ping the LAN address (192.168.1.2).  However, I am still unable to SSL (https://) into pfsense.  Also, after setting the second LAN adapter (linux) to pfsense LAN address, I am still unable to reach the Internet.

    Also, to answer your question, I didn't set pfsense to be a DHCP server.

    All my other virtual machines are set as 'bridged' adapters, which work fine since they receive IP addresses from my router.  I have just recently set linux's LAN adapter to intnet as you suggested, which brought about a successful LAN ping.

    I'm still puzzled.

    Thanks for any further suggestions.



  • @amer1canparatrooper:

    Also, after setting the second LAN adapter (linux) to pfsense LAN address, I am still unable to reach the Internet.

    It is not clear to me what you mean by the above sentence. Did you set a second network adapter in the Linux machine to have IP address 192.168.1.2? If so, that probably explains what you are seeing in the second ping of your screenshot. I presume the screenshot shows activity on that Linux VM. The ping of 192.168.1.2 responds since 192.168.1.2 is a local address. The ping of 10.0.1.105 gets "Destination host unreachable" since the local machine doesn't know how to get to 10.0.1.105. Your Linux VM needs a default route AND a distinct IP address, apparently on the 192.168.1.x/?? subnet.

    Also, to answer your question, I didn't set pfsense to be a DHCP server.

    All my other virtual machines are set as 'bridged' adapters, which work fine since they receive IP addresses from my router.  I have just recently set linux's LAN adapter to intnet as you suggested, which brought about a successful LAN ping.

    I'm still puzzled.

    Thanks for any further suggestions.


Log in to reply