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

    Adding in NIC drivers into pfSense

    Problems Installing or Upgrading pfSense Software
    2
    5
    2.4k
    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.
    • C
      CryptoMithrandir
      last edited by

      I'm new to pfSense/FreeBSD and I have looked but haven't found much about trying to get a newly installed Intel i350-T4 NIC setup for pfSense.  What I did see was that I had to compile to drivers in a live/VM version of FreeBSD that runs pfSense 2.3.3, then import a file back into my install, OR by trying a reinstall pfSense 2.3.3.  I have tried the second one, but no luck it just shows my motherboard NIC as available.  My next step is to try a version of pfSense 2.4.

      1 Reply Last reply Reply Quote 0
      • P
        pfBasic Banned
        last edited by

        :o

        That's all crazy.

        Plug a monitor and keyboard into your pfSense, shut it down, plug the card in, start it back up, reassign the NICs. Done.

        1 Reply Last reply Reply Quote 0
        • C
          CryptoMithrandir
          last edited by

          @pfBasic:

          :o

          That's all crazy.

          Plug a monitor and keyboard into your pfSense, shut it down, plug the card in, start it back up, reassign the NICs. Done.

          I tried that, but once it finally came back up it still showed that the mobo NIC is the only one available.  Even after a re-install.  I'll be trouble shooting this further this weekend, but thought I would see if anyone had any suggestions.

          1 Reply Last reply Reply Quote 0
          • P
            pfBasic Banned
            last edited by

            might be a hardware problem, have you tried the NIC in other machines to confirm it is working?

            What is the model # of your motherboard?

            1 Reply Last reply Reply Quote 0
            • C
              CryptoMithrandir
              last edited by

              Just found my solution, turns out it was the PCIe slot I was using was bad, so I moved it up one and it's working now.  Thanks for the suggestions.

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