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

    pfSense on Proxmox - Internal lan not working

    Scheduled Pinned Locked Moved
    Virtualization
    2
    4
    1.5k
    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.
    • T
      tcaldon
      last edited by

      Hi,
      i'm new to pfSense and i'm trying to setup it with proxmox on my home lab with this setup:

      • eth0 -> connected to internal router (192.168.4.1)
      • vmbr0 -> bridge of eth0 (wan), model: intel e1000 to pfSense VM
      • vmbr1 -> bridge of eth0 (lan for my VM), model: intel e1000 to pfSense VM

      With pfSense i can ping everything without problems (ex. 1.1.1.1 or google.com) but with a Windows VM on the same host i can only ping IP (ex. 1.1.1.1) and i can't ping domain (ex. google.com)

      I've checked out the guide of this guy here (https://www.youtube.com/watch?v=Iny-4Gu_Vb4) and also remade the VM with the netgate Guide (https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-proxmox-ve.html#virtualizing-with-proxmox-ve) but haven't got any progress..

      Does anyone know what could be the problem?

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @tcaldon
        last edited by

        @tcaldon said in pfSense on Proxmox - Internal lan not working:

        but with a Windows VM on the same host i can only ping IP (ex. 1.1.1.1) and i can't ping domain (ex. google.com)

        So the VM obviously cannot resolve host names. What DNS server does it use? Did you configure the interface in the VM manually or is it configured by DHCP?

        BTW:
        The Netgate guide you've quoted, suggests to use the virtIO network interface. So why you're using e1000?

        Furthermore why did you connect vmbr1 to eht0? Since this bridge is intended for internal VMs only, there is no need to connect it to a physical interface.
        Having both, WAN and LAN, connected together may result in routing issues.

        T 1 Reply Last reply Reply Quote 0
        • T
          tcaldon @viragomann
          last edited by

          @viragomann sorry i write down some mistakes..

          Let's give a point to point answer to you:

          • What DNS server does it use? Did you configure the interface in the VM manually or is it configured by DHCP? -> I've tried to use pfSense DHCP as a standard and it didn't work.. Later on on the Windows VM i've configured a static IP in the pfSense LAN range and static DNS that i've force to point to the pfSense also forcing it did not work

          • So why you're using e1000? -> in the video that i linked the guy uses e1000, and before writing down on this forum i've see a lot of article that written about problems with virtIO interfaces but... i've just tried to setup the VM with the Netgate guide and i'm stuck at the same point

          • Furthermore why did you connect vmbr1 to eht0? -> sorry, i've write it down wrong. I've connected vmbr0 with eth0 and vmbr1 is not connected to anything that goes out of proxmox, i've created it only for internal connectivity

          T 1 Reply Last reply Reply Quote 0
          • T
            tcaldon @tcaldon
            last edited by

            EDIT: just change some DNS Resolver settings, like the outgoing network interfaces (selected only WAN), disable DNSSEC, enabling Forwarding Mode and also disable IPv6 on WAN and LAN on the interfaces setting and now it's working!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post