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

    PfSense in VirtualBox on Ubuntu server - Can't get WAN IP

    Scheduled Pinned Locked Moved Virtualization
    5 Posts 3 Posters 5.7k 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.
    • R
      RAND0M1ZER
      last edited by

      Hi, I'm tring to install pfSense on my headless Ubuntu 12.04 server. I have installed the pfSense VM but I need some help getting the network cards configured correctly.

      My server has 2 Intel NIC called eth0 and eth1. I have setup my pfSense VM to have 2 NICs in bridge mode and I can connect to the pfSense GUI from my network however pfSense can't seem to get an IP from my cable modem.

      Any idea what could be wrong?

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        your vm nic is going to have a different mac I would assume - so reboot your cable modem.  This is normal procedure when changing the mac of the device connected to a cable modem

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

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

          I've tried that rebooting the VM, the physical server, and the modem multiple times with no success.  >:( Do bridge connections require any kind of configuration on the host side of things?

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

            I have the same configuration and have encountered the same problem. I was able to get a DHCP assignment from another device so it seems that the nic and virtual br1 are configured correctly. Hmm??

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

              I actually fixed it and got it working. Turns out I had to configure the WAN interface on the host side.

              My /etc/network/interaces file now looks like this:

              # This file describes the network interfaces available on your system
              # and how to activate them. For more information, see interfaces(5).
              
              # The loopback network interface
              auto lo
              iface lo inet loopback
              
              # The primary network interface
              auto eth0
              iface eth0 inet static
              address 0.0.0.0
              
              auto eth0:1
              iface eth0:1 inet static
              address 192.168.0.2
              netmask 255.255.255.0
              gateway 192.168.0.1
              dns-nameservers 192.168.0.1
              
              # The WAN interface
              auto eth1
              iface eth1 inet static
              address 0.0.0.0
              
              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.