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

    Virtualized pfSense - no WAN IP due to cable modem + Windows 10?

    Virtualization
    1
    1
    316
    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.
    • J
      jhuang0
      last edited by

      I've got a VirtualBox setup on Windows 10 that has an issue getting a WAN IP from my cable modem (Netgear 1100). The Windows 10 host OS talks to the cable modem first and is able to acquire an IP address that allows the host operating system the ability to surf the internet. From what I've been able to piece together, the reason why my pfSense instance is not able to get an IP might be that the cable modem has locked on to the Windows 10 physical MAC that the cable modem is connected to. By the time pfSense gets around to it, the cable modem won't talk to the virtualized pfSense instance.

      Can someone correct me if I'm wrong? If I'm right, is there a way to configure Windows/VirtualBox so that I don't have this issue?

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.