How often do NICs fail?

I am running pfSense on a Dell SFF.
IBM Quad Port Adapter 39Y6137 39Y6138 Intel pro 1000 PCIE Gigabit Ethernet adapter
It’s been running 24/7/365 for about 4 years now, and has generally been rock solid.

Started having connectivity problems yesterday.
pfSense would detect ports, then not:
Configuration references interfaces that do not exist: em0, em1, em2, em3
Network Interface mismatch – Running interface assignment
Valid interfaces are:
No interfaces found:
pfSense cannot continue without at least one Network Interface

Am I right to suspect the network adapter?
Everything fails, but is this reasonable?

That sounds like the network card to me also.

1 Like

Yeah, eventually cards will go bad. I replaced a 10gb card a few months ago because things were just going slow. Could have been the card, could have been the SFP+ module, replaced both and everything back to normal. Card and module were more than 10 years old.

FYI, you can get an Intel i350 based card brand new for around $80, this is what I’m putting in my new firewall. Intel i225/i226 based cards can be had for a little more.

1 Like

Thanks all.
When the problems started happening I just thought: “Must be disk that died”.
Did not suspect the NIC.

I see Intel based and Broadcom based cards.

Could try taking the card out of the machine, and reinserting it - to see if this makes any difference

1 Like

In general, Intel based seems to work better for this. And without the latest Realtek drivers, Realtek is out.

1 Like

Thanks Paul. No joy. The NIC has solidly failed now.
Got a new IBM INTEL 1340-T4 Quad Port Gigabit Ethernet PCIe Network Adapter on the way.

Thanks got a new Intel based 1340-T4 Quad Port Adapter on the way

Just got new network card and installed it. pfSense now seems to recognize interfaces.
I installed new disk and reinstalled pfSense.
Noticed that the new card interfaces come up igb0, 1, 2, 3.
Old card used to be em0, 1, 2, 3
New pfSense install is not handing out address and I cannot log into it from lan pc.
No idea why LAN pc is not getting address.
I want to reload old config file, but worried about igb vs em numbers for ports.
Any thoughts?

In the console you can reassign the interfaces to the new physical names. Then once you have web gui access you can then reassign all the VLAN interfaces to the new parent interface.

After you got the new card installed it should have promoted you to assign the new interfaces. If not might be able to reboot to get the prompts again. I’m not talking about the web GUI I am talking about a monitor hooked up or the console.

You can also edit the config backup, but you’ll still need to have at least one interface that allows you to get into the system (I think). I can’t remember if you can restore a backed up config from the VGA terminal.

Also I thought that if you had a USB drive (fat32) with the backed up or edited config, and you reinstallled the system, it would load that config during the process. Or is this an OPNsense thing only.

I am able to connect to pfSense, but pfSense is not connecting to my cable modem (WAN).
I can connect to the cable modem directly with my PC.
See attached screenshot of pfSense status page.
I am using pfSense 2.7.2
Notice that dpinger Gateway Monitoring Daemon is not running (and won’t start)
WAN interface is showing up but will regularly go down and then right back to up.
WAN DHCP (IPV4) is not showing in the Gateways…I have it in the setup.
So “once again” I am stumped.

Status > System Logs > Gateways will tell you why it is not getting WAN

1 Like

Seems to repeat:

Mar 31 14:13:23 dpinger 23969 WAN_DHCP 97.88.218.1: sendto error: 65
Mar 31 14:13:23 dpinger 23969 WAN_DHCP 97.88.218.1: sendto error: 65
Mar 31 14:13:24 dpinger 23969 WAN_DHCP 97.88.218.1: Alarm latency 0us stddev 0us loss 100%
Mar 31 14:13:24 dpinger 23969 WAN_DHCP 97.88.218.1: sendto error: 65
Mar 31 14:13:24 dpinger 23969 WAN_DHCP 97.88.218.1: sendto error: 65
Mar 31 14:13:25 dpinger 23969 WAN_DHCP 97.88.218.1: sendto error: 65
Mar 31 14:13:25 dpinger 23969 exiting on signal 15
Mar 31 14:13:31 dpinger 85490 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 97.88.218.1 bind_addr 97.88.218.134 identifier WAN_DHCP
Mar 31 14:13:32 dpinger 85490 exiting on signal 15
Mar 31 14:13:32 dpinger 10162 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 97.88.218.1 bind_addr 97.88.218.134 identifier WAN_DHCP

replace your rj45 cables for WAN, LAN.

Just FYI there are alot of fake intel quads out there on ebay. I ended up with a couple of fakes which worked fine in pfsense but started to have weird issues after a year. So I did some research on how to spot real deals vs fakes.

I will dig up a link to the article on how to spot them.

EDIT: Below is the link to the article. For me I was buying the i350-T4 as it’s known to work fine in pfsense.

1 Like

I’d be interested in that regardless of whether the one I bought is a fake or not.
:+1:

Error 65 is ‘no route to host’, so it means you have no route to the gateway at that time. Either it’s not in your subnet or somehow the interface doesn’t have a route to its subnet.

I edited my post to include the link.

Guess I got the V2, date is 08/2016

Every single other feature in the real/junk comparison points to it being real. I guess I’ll have to see how long the 10Gtek branded one I bought lasts, at least they aren’t trying to deceive you into thinking it is genuine Intel. I probably should have splurged for the i226 cards.