Intel Quad Port NIC- Works for Minute, then times out when pinging/can't access?
-
Hello everyone,
I have an Intel 82579? Silicom Quad port NIC that I got to use for VMs. However, whenever I use it for PFSense, whether directly on a PFsense box or through Hyper-V, it works for about 1 minute and then it doesn't respond to pings and trying to access web interface just results in it timing out.I have tried doing the IGB tweaks like increasing MBUFs but nothing works, it just will not respond. Anyone have any ideas?
-
@servergeek
Cables, slots, ports assigned to vSwitches. Move them around some as possible. Could be a bum card or port. -
It happens on all the ports, not really sure why. The card works normally for other stuff like Windows guests though, so I don't really understand what the deal is.
-
-
Are those the only ports in the system? Do all the ports fail at once?
I'm not aware of ever seeing an igb NIC fail like that. It seems more likely the network stack stops responding for some reason unless you have evidence it does not.
Steve
-
It's kinda wierd what happens. From inside the PFSense box I can update it from the WAN side, but from the LAN side DHCP works, but there's no internet connection and attempting to ping it/access web interface just results in it timing out.
It happens every time on the LAN side regardless of what port configuration I use.
-
But WAN and LAN are both using ports on that card?
So DHCP continues to work on LAN when other connectivity fails?
That sounds a lot more like a rule problem. If you have DHCP enabled on an interface it will always allow dhcp requests in even if there are no other rules or only block rules.
Steve
-
@stephenw10 It's on a fresh install, no rules set yet. After I go through setup it just stops working.
This happens when having a separate card as a WAN port and then using the NIC as the LAN/OPT interfaces, or just using the NIC as the WAN/LAN interfaces
-
Ok, only the actual LAN interface has any rules by dedault. If you're testing on ab OPT interface and have not added any rules that is the expected behaviour. DHCP works, nothing else passes.
Steve
-
@stephenw10 I am testing on the LAN interface. It happens on the LAN interface right after running the initial setup.
-
Also, apparently it is a Intel 82576-based card, with 2 dual port controllers on it. Not sure if that makes any difference.
-
Does DHCP actually continue to work after everything else fails?
Or just that it has already worked and remains on that IP for the duration of the lease?
Steve
-
@stephenw10 It still hands out leases, I was able to release and renew and got a new IP.
-
Hmm, weird. I guess I'd try a packet capture. See if anything is actually coming in at all.
Other than dhcp broadcast requests which might be a clue.
If setting the pcap in promiscuous mode suddenly allows traffic to pass again it's some ARP/MAC problem.
The time span you mentioned does sounds quite ARP like...
