Steve, my bad.  I see it.  I was expecting to see 8111e but I see it as 8111G.

Link should be: https://forum.pfsense.org/index.php/topic,62032.0.html Steve

Wrong to delete all files in boot/kernel. But does not matter. Problem should be solved in the new 2.1 release. Upgrade or reinstall to fix issue. Probably a better solution.

i3 3220 does, and it's friends will work. i3 4330 does as well and it's friends should work as well. different socket but same principle. Intel's basically throwing low cost servers a bone.

That box has two 50W TDP processors in a 1U enclosure, it's going to be loud.  ;) Potentially way too loud though it has thermal fan speed control so if you are only using it for light duties it will be quieter. Also it's far more powerful than you need for a home box. Unless you've got a crazy speed home connection.  :) Steve

Thanks for your feedback

My worked fine when I first received it, even though it had been badly packed and damaged in transit, then one day it just didn't boot. Symptoms just like yours, arm/disarm LED doing something it shouldn't at power on. The previous owner may have known nothing about it. Steve

They might - If anything gives you problems it will the the RTL8111D NICs.  Same in both boxes. You could try it with one before you buy 10,000 units. Thing to watch with the Chinese guys there is you need to be sure they don't change specs on you. Some Chinese companies seem to not know the value of maintaining a certain product line more than 5 days yet.

Yep - Those work.  I have gotten then for $20ish http://www.ebay.com/itm/INTEL-DUAL-PORT-GIGABIT-ETHERNET-NIC-SERVER-ADAPTER-NC360T-HP-PROLIANT-DL160-G6/130986855852?_trksid=p2047675.m1850&_trkparms=aid%3D333005%26algo%3DRIC.FIT%26ao%3D1%26asc%3D12%26meid%3D1466837804531550502%26pid%3D100011%26prg%3D1005%26rk%3D2%26rkt%3D5%26sd%3D171056854896%26

So I compiled em-7.3.8 on a FreeBSD-8.3 virtual machine. I am successfully able to load that driver during boot for the virtual machine and everything seems to work. I moved the driver over to PfSense's /boot/modules, gave proper 555 permissions, and added 'if_em_load="YES"' to /boot/loader.conf.local. My PfSense would hang when booting on "configuring WAN interface". ifconfig in single user mode showed the interfaces seemed to work with the new driver, maybe I need to reconfigure my interfaces for pfsense? I can try it, I'll do it tonight when I have more time. What's weird is I'm pretty sure this NIC worked flawlessly with PfSense 2.0.1 when I used it over a year ago.

Sounds like you have the idea.  Have fun! :) Steve

For anyone not following the 'G' thread a much newer driver is now available to test here: http://forum.pfsense.org/index.php/topic,65355.msg365028.html#msg365028 Steve

Great ! Thank you Steve.

Yes, pfSense just sees them as NICs. You can assign them to WANs or LANs or configure a more complex setup that blurs the lines.  :) Steve

That looks like it should be a Realtek chip, is that right? Careful with your bits and Bytes there!  ;) Steve

Maybe but you'd have to access it directly since you can't boot anything from which to read it. Sonicwall seem to have gone to some length to prevent it being modified. It would be interesting to get another opinion on it though. See what you can find. Steve