Can not get DHCP leases on new intel I225-LM based machine
-
Mmm, we haven't seen any issues like that on the i225/226 NICs we have. But, yeah....
-
I think there must be some sort of conflict between AMT & DHCP Server function with I225 NIC.
So far, I couldn't get DHCP Server to work if I225-LM has AMT enabled.
The temporary solution for DHCP Server to work is disabling I225-LM's AMT function.
Not sure if this is also the case with I226 NIC tho. -
I have the same ASRock NUC.
How can I disable the AMT function ? On my NUC Bios ?
3 months after having bought this unit, I still cannot use it as I would like and if I don't find a solution, I will resell it.
-
I have the Intel NUC 11 Pro Kit NUC11TNHv70L, which also has a 2.5GB Intel Ethernet Controller I225-LM NIC. I have pfSense installed and have also pulled out my hair for the past three weeks, trying to set up pfSense on Proxmox on the NUC. I've followed all the instructsions for Proxmox, and I've also chatted quite a bit on discord with some experts on Proxmox.
I've set up packet capturing on both clients and server (pfSense), and I'm experiencing the same.
DHCPACK and DHCPOFFER packets are sent from pfSense, but they do not go beyond the network card. They are never received by the client. When I came across this thread, I thought I had my answer. I was using AMT. So I disabled it, but the issue remains.
When I swap DHCP servers to another one on my network, everything works great. When I swap the LAN interface on pfSense to use a USB-Ethernet plugged into the NUC and set up on Proxmox as a Linux Bridge, that also works great.
But using the Intel Ethernet Controller I225-LM does NOT work with pfSense's DHCP Server. I've tried PCI direct. I've tried Linux bridges. I've tried everything.
DHCPACK and DHCPOFFER packets are not received by the client. Something is preventing the packet from going beyond the Intel Ethernet card. There is an issue with this card and pfSense's DHCP Server or with this card and DHCP Server's in general.
I hope someone can figure out why and provide an update/fix.
-
How did you deactivate the AMT function ?
I have an ASRock 1220p.
Thanks
-
@Richard-1
I think AMT needs to be disabled by SMBus or CSME settings in order to get DHCP Server working.
You should contact ASRock for further assistance. -
@curiousAboutDHCP I have exactly the same issue with I226 NIC. Have you found any solution to this problem?
-
What chip exactly?
I'm not aware of any solution for this in pfSense though. BIOS/firmware fix only as far as I know.
-
@stephenw10 I'm now having the exact same problem on a minisforum ms-01. "i226-LM" and from what i read its the same with the other port on my computer "i226-V".
I think this is a issue in Linux kernel driver "igc". In my case i run pfSense in Proxmox 8.2 with kernel "6.8.8-3-pve".
But i don't know that much really i'm not a programmer.. or even close to it..
https://www.intel.com/content/www/us/en/products/sku/210595/-intel-ethernet-controller-i226lm/downloads.html
Might be related. What if it could be fixed with a driver in pfSense? I don't understand it at all really but trying to learn.. I don't even know how to try that later version or to figure out what it's dependencies are.
-
@thewho said in Can not get DHCP leases on new intel I225-LM based machine:
I'm now having the exact same problem on a minisforum ms-01.
Yup it's a known issue on that device, there's a thread here detailing it. One of those NICs has the Intel vPro OOB access enabled on it and that somehow prevents DHCP working. Try the other i226 NIC.
-
@stephenw10 Yeah! Sorry for that! i ended up using a x710 also on the board for LAN.
Still having lot's of weird issues but can't really what they are more then that they come and goes... might be a really unstable NIC..
-
Anything logged?
