Bug #8081
closed
NICs malfunction
0%
Description
On a firewall with 8 NICs:
igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb2: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb3: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb4: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb5: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb6: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
igb7: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k>
After updating to 2.4.1 I start to have problem on NIC igb2 and igb3, connected to switches Allied X510: interfaces stop working without any indication in gui
NICs igb4, igb5 and igb6 are connected to external routers and they work fine.
Deactivating and reactivating NICs igb2 and igb3, they start working fine.
Restarting the firewall the problem, sometimes, returns.
Updated by Braden McGrath about 7 years ago
I'm having a similar problem, which persists into 2.4.2, with igb interfaces. The problem exhibits itself for me with the interface actually flapping down and up repeatedly at the physical level (der blinkenlights go off and back on repeatedly). On my situation, it was igb1 which is my LAN interface, and then I reconfigured the system to use igb2 as LAN instead and the problem persisted there, so I'm pretty sure it's software-related and not hardware.
The only fix I've found so far has been to hardcode speed & duplex on the pfSense side to 1000FDX, which is not really the best solution.
Oddly, igb0 for me hasn't acted up... yet.
I didn't have these problems in 2.3.x, and I'm not sure if I was on 2.4.0 long enough for it to crop up. However, I've had a similar issue in the past (maybe 2.0 or 2.1?) with completely different hardware (but still Intel NICs using igb(4) driver).
I have a forum thread going over here: https://forum.pfsense.org/index.php?topic=139921.0
Updated by Jim Pingle over 5 years ago
- Category changed from Interfaces to Hardware / Drivers
- Status changed from New to Closed
This report is from a few pfSense and FreeBSD versions ago. Please re-test this on a current release. If there is still a problem, re-test on a development snapshot. If there is still a problem, it can be reopened, but it's almost certainly an upstream FreeBSD issue that needs resolved there.