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

    nic 2.5 not working.

    Scheduled Pinned Locked Moved Hardware
    30 Posts 6 Posters 4.1k 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.
    • T
      tedquade @Dobby_
      last edited by

      @dobby_ I have an appliance with i225-V inbuilt components. Do you know of a method of determining the version (visual inspection, some application, etc.)?

      Ted Quade

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        It's shown as the revision in the output of pciconf -lv:

        [23.01-RELEASE][root@6100-3.stevew.lan]/root: pciconf -lv igc0
        igc0@pci0:4:0:0:	class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
            vendor     = 'Intel Corporation'
            device     = 'Ethernet Controller I225-V'
            class      = network
            subclass   = ethernet
        
        T 1 Reply Last reply Reply Quote 1
        • T
          tedquade @stephenw10
          last edited by

          @stephenw10 I have version 1. Can someone point me to information about known problems so I can avoid bugging Pfsense / forum folks unnecessarily.

          Ted Quade

          Dobby_D J 2 Replies Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            The issue as reported is that the i225-v NICs will spontaneously disconnect at random. I have one device with an older rev NIC though and I've never seen that.

            1 Reply Last reply Reply Quote 2
            • Dobby_D
              Dobby_ @tedquade
              last edited by

              @tedquade said in nic 2.5 not working.:

              @stephenw10 I have version 1. Can someone point me to information about known problems so I can avoid bugging Pfsense / forum folks unnecessarily.

              Ted Quade

              Your only chance as I see it is to follow the tip of @stephenw10 so if there is an patch or fix, I am pretty
              sure it was running into FreeBSD 14.0 and with some luck
              on your site it is done. If not it should be finding its way into
              14.0 Current as I was reading it in the internet else where.

              #~. @Dobby

              Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
              PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
              PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)

              1 Reply Last reply Reply Quote 1
              • Dobby_D
                Dobby_ @kp206
                last edited by

                @kp206 said in nic 2.5 not working.:

                should i look on amazon or look into name OEM brands like, Dell, Lenovo or HP?

                You can do, but often I would then try out to install the original firmware from Intel if you will be able to get
                your hands on.

                #~. @Dobby

                Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
                PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
                PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)

                1 Reply Last reply Reply Quote 0
                • J
                  JimBob Indiana @tedquade
                  last edited by

                  @tedquade As Stephenw10 I’ve never had any issue with the Intel 2.5gb NIC’s. I’m using version 3’s though.

                  1 Reply Last reply Reply Quote 1
                  • K
                    kp206
                    last edited by

                    Here's an update. I installed this and it works with pfSense. 😊

                    https://www.amazon.com/dp/B0BNHWZBCC?psc=1&ref=ppx_yo2ov_dt_b_product_details

                    Screenshot 2023-05-03 at 11.13.07 AM.png

                    1 Reply Last reply Reply Quote 0
                    • G
                      gerbildral
                      last edited by

                      Hi,
                      I have a NUC (nuc11tnhv50l) where i passthrough the 2 onboard i225-LM nics to pfsense, but i can't get dhcp to work on the LAN interface. this is the only message i see in the logs:
                      5bddf460-f0b5-4b47-bf08-7215c17bc22f-image.png

                      i have checked the ref(it is the v3), i have checked the firmware(i it 1.57), i tried a usb nic(dhcp works fine then), i even tried the dev build (2.7.0-DEVELOPMENT, also doesn't work), i disabled checksum offloading(didn't do anything)
                      the strange thing is that it is recieving DNS suffix etc but no ipv4 addresses.

                      do you guys have any idea where i can look to find a fix?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        It's seeing the request and replying to it. What happens to that traffic? Can the client see it in a packet capture?
                        Does it work if you don't use hardware pass-through?

                        G 1 Reply Last reply Reply Quote 0
                        • G
                          gerbildral @stephenw10
                          last edited by

                          @stephenw10 It can't discover the dhcp server, in wireshark you can see it is asking for the dhcp server but is getting no response eventhough my pc is directly connected to the LAN port
                          6d4128c2-e0cf-4785-b86c-39abee227c0c-image.png
                          if i connect to a working network i connects immediately.
                          i also tried bare metal but i still get the same issue, and the bridges in proxmox also don't work

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Hmm, sounds like a hardware issue if Proxmox can't use them either.

                            What if you assign LAN as the other NIC, presumably igc1?

                            G 1 Reply Last reply Reply Quote 0
                            • G
                              gerbildral @stephenw10
                              last edited by

                              @stephenw10 unfortunately switching the interfaces also don’t work. Tomorrow I’ll do some tests with the nuc on windows to see if it wants send out dhcp so i see if it is going to be a RMA or not :)

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