nic 2.5 not working.
-
https://forum.netgate.com/topic/159994/intel-ethernet-controller-i225-lm-support/17?_=1682292195982
That’s one thread.
-
Another:
https://forum.netgate.com/topic/166952/2-5-gbps-hardware/21?_=1682292195985
-
Hmm, OK this post certainly seems to imply the NICs were not recognised at all with hardware checksum offloading enabled. Though it's hard to see how that could possibly be since that setting only affects how NICs are configured and that can't happen if they're not recognised. Easy to test though.
-
@stephenw10 That’s what happened when I first tried the 2.5 Intel NIC’s. Not found until was able to change the options, saved, booted, Intel cards found.
2.7 did not require the same option selections.
-
It is an Intel i225-V adapter, but witch revision is it in real?
i225-V (version 1) - known problems
i225-V B2 (version 2) - known problems
i225-V B3 (version 3) - makes no problemsIntel i225-IT/AT - no problems
Intel i225-LM - no problems
Intel i226 - no problems, but support starts at pfSense 2.7So be sure to not getting any problems you may install an
adapter (NIC) such as Intel i225-IT or i225-LM or if you try
out pfSense 2.7 you will also good sorted with an Intel i226
adapter. -
@stephenw10 thank you for your help!!
-
@dobby_ Thanks, should i look on amazon or look into name OEM brands like, Dell, Lenovo or HP?
-
@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
-
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 -
@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
-
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.
-
@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. -
@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. -
@tedquade As Stephenw10 I’ve never had any issue with the Intel 2.5gb NIC’s. I’m using version 3’s though.
-
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
-
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:
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?
-
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? -
@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
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 -
Hmm, sounds like a hardware issue if Proxmox can't use them either.
What if you assign LAN as the other NIC, presumably igc1?
-
@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 :)
