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

    Fresh installation in virtualbox; can't ping pfsense IP

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 3 Posters 4.2k 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.
    • A Offline
      alphajoza
      last edited by

      I've installed pfsense 2.3 x64 in virtualbox with 2 adapters; One is bridged to my wifi adapter (adsl modem) (WAN) and the other one set as'Internal network' ('intnet') (Lan);

      The problem is that although pfsense can automatically detect dhcp over first adapter and get an IP but my system (the host) can not ping the pfsense server (pfsense can ping both adsl modem gateway and the host).

      Note1: Disabling the antivirus and firewall (kaspersky internet security 2016) has no effect.

      Note2: I know that this setup works because I use the exact same network configurations for a Kerio Control server (v9.0.2, installed in virtualbox)

      Note3: If I constantly ping pfsense server in my host (ping 192.168.1.102 -t) and at the same time restart pfsense server, during the booting phase of pfsense I can get two pings!


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

        WAN interface blocks everything by default.

        The two pings occur between when the WAN interface comes up and the firewall gets applied.  Which may be a potential security hole.

        1 Reply Last reply Reply Quote 0
        • A Offline
          alphajoza
          last edited by

          So what should I do? try to connect to server via LAN?

          1 Reply Last reply Reply Quote 0
          • C Offline
            cmb
            last edited by

            Option 12 at console, "playback enableallowallwan", and it'll unset the block private networks and add an allow all rule. That's probably where you want to start since WAN is actually on LAN, but that's not something you want if that WAN will be moved to an Internet connection.

            1 Reply Last reply Reply Quote 0
            • A Offline
              alphajoza
              last edited by

              I tried to connect to pfsense via client in LAN (as suggested) and it was successful;

              Thanks for the clarifications

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

                @alphajoza:

                So what should I do? try to connect to server via LAN?

                I use host only adapter for the LAN interface and set its network to something like 192.168.249.0/24.

                Configure the pfSense LAN with 192.168.249.1 via console option 2 and then the host machine can access pfSense via it's LAN interface.

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