I've suddenly lost the device that tied to one of my interfaces. It just says "igc3 (missing)" under Device. I don't know if this is a hardware problem (the Ethernet port is bad in my router) or if it's actually an OPNsense issue.
Can anyone help explain what this means and/or how to fix this?
It means it's assigned but not found currently. Since it's a hardware device did you switch hardware? If not the driver doesn't attach to that port anymore it seems and the NIC could be fried.
Cheers,
Franco
Basically what Franco said.
As these are igc we can assume its Intel i225/i226.
You could try to review dmesg if the igc3 is seen there if there is any related message regarding it. If nothing I would try to live boot a linux distro from a USB and check if it sees that specific interface.
But most likely, on first look, it looks like that NIC is gone as its not communicating.
Regards,
S.
Thank you for the replies. That's what I was afraid of. My router is a Protectli VP2420. So, I guess that means that port is permanently dead now?
Last week, I had attached a new Unifi Dream Machine SE to that port because I installed security cameras and that was my NVR. Then five days later, I got the dreaded "Plug In Cable" error on the UDM-SE. Unifi support had me move the cable from the WAN port to another port to diagnose ("If it doesn't work on port 8, then the unit needs an RMA.") I didn't think about it in the moment, but port 8 is a POE+ port. Does it seem plausible that the POE+ port (or the WAN port) could have fried the port on the Protectli?
If it is "modern" POE, then no, it should not be able to fry your computer port.
I would plug that protectli port into some other device and see if it works after a full shutdown, remove power for 30 seconds to a minute, then power it back up and see what happens. Best if you have one of the cheapo dumb switches hanging around, doesn't matter if 10/100 or gigabit/multi-gig, just a plain old dumb switch. If you don't have one, a lot of newer laptops should be OK without a cross over cable.
Also try a different cable with the above tests, just to make sure the cable didn't go bad and short a bunch of conductors. This really should give a different error, but you never know.