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

    vmx NIC ordering for pfSense on vSphere 5.5+

    Scheduled Pinned Locked Moved Virtualization
    6 Posts 5 Posters 1.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.
    • S
      shawnrhode
      last edited by

      When adding a 5th VMXNet3 NIC to a pfSense guest running on vSphere 5.5+, the NIC ordering gets mixed up. Example:
      4 vmxnet3 NICs:
      NIC1 = vmx0
      NIC2 = vmx1
      NIC3 = vmx2
      NIC4 = vmx3

      5 vmxnet3 NICs:
      NIC1 = vmx0
      NIC2 = vmx2
      NIC3 = vmx3
      NIC4 = vmx4
      NIC5 = vmx1

      This occurs during initial install as well as if you change the configuration later on. In the latter case, this can really make things complicated because the configuration for a given NIC isn't bound to the MAC address so the configuration on the system slides around and isn't correct after reboot. This can make access not function, especially in the common case where vmx0 is WAN and vmx1 is LAN.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That's a known issue and has been that way for years. It really doesn't have anything to do with pfSense or VMXNET though, ESX will reorder the NICs after adding the 5th one no matter what the guest OS is running.

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        R 1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          Yeah that's a fun esx feature

          1 Reply Last reply Reply Quote 0
          • awebsterA
            awebster
            last edited by

            One solution to keep NICs to a minimum is to use VLANs instead.
            IE: set your VMNIC on vlan 4095 (all vlans) and then pop them off as needed inside pfSense.

            โ€“A.

            1 Reply Last reply Reply Quote 0
            • R
              raitd @jimp
              last edited by

              @jimp I've seen many linux distro's handle having several nics in vmware and handle adding more perfectly fine. Does pfSense / FreeBSD have an option where you can force binding to a particular MAC address? If so I imagine many people would love to have this as a selectable option.

              Also, just using VLANs in pfSense doesn't give you enough options with things like traffic shaping.

              jimpJ 1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate @raitd
                last edited by

                @raitd said in vmx NIC ordering for pfSense on vSphere 5.5+:

                @jimp I've seen many linux distro's handle having several nics in vmware and handle adding more perfectly fine.

                Linux is vastly different in their default naming schemes. The current default names in Linux are based on bus locations which likely wouldn't change in those cases. FreeBSD counts up from 0 for each instance of the driver it finds when probing, so if the probe order changes, so does the NIC assignment order.

                Does pfSense / FreeBSD have an option where you can force binding to a particular MAC address? If so I imagine many people would love to have this as a selectable option.

                No.

                Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

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