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

    ESXI and VLAN

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 530 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.
    • B
      bjokib
      last edited by

      I am running a fresh esxi 6.7 install and trying to Get pfsense on a VM.

      I connect to Internet via a fiber connection. I just use vlan 102 on the media converter and I Get a public ip.

      So far I am Unable to Get an ip on the VM. The server have four physical nics But when i set up vlan on the nic that is connected to the media converter pfsense dosent Get a public ip. Internal LAN ip works fine.

      I followed this guide: https://doc.pfsense.org/index.php/PfSense_on_VMware_vSphere_/_ESXi

      My older dedicated router computer work so the physical Network should be fine. Any idea how to Get this Setup working? Thanks  :)

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

        Saying you followed guide X doesn't mean you actually followed it correctly, etc..

        Your going to have to show us your network in esxi..

        So you created a vswitch, connected to physical interface.  If you want the wan vnic of pfsense that is connected to that you either set your vlan ID on the vswitch port group, or you set 4095 on it to not strip tags and then setup your vnic in pfsense to understand the tag you want it to use.

        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
        • B
          bjokib
          last edited by

          Fantastic, setting the vlan id 4095 on the WAN port group solved the problem. Thank you for the assistance, highly apprechiated. :)

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