NIC Missing after Attempting LAN Bridge on WatchGuard 505
-
Hey, apologies if this isn't the right place, but wasn't having much success finding information to help elsewhere.
I recently acquired an old WatchGuard 505 and planned on running it as a replacement for my standard router. I successfully got PFSense running on it after removing the VPN accelerator card and WatchGuard OS CF card, and swapped in more ram, a Core 2 processor, and an SSD. Everything seemed to be running fine, with the exception of my em3 NIC, which wouldn't initiate.
After Attempting to configure a LAN Bridge across all my NICs, excepting my designated WAN, the WebUI became mostly inaccessible and I ended up going for a factory reset through the Console port. Upon reloading, I'm no longer seeing my em5 NIC listed as an option, active or otherwise; even running
pciconf -lvisn't showing it anymore.Attempting a CMOS clear doesn't appear to have any effect, and neither are resets.
I'm not having much success trying to bring this back up. Any recommendations or thoughts as to what my have happened?
-
It only shows 5 em NICs in pciconf?
How is em3 failing, the driver doesn't attach?
Hardware not showing on the pci bus doesn't bode well though...
Steve
-
Apologies for the delay in my reply. Well, went for another CMOS clear, reset, and reboot and not only is the NIC back up, but it shows in pciconf now. I was able to successfully configure my bridge as originally intended.
That said, I'm still getting the message,
em3 :Hardware Initialization Failed, and that NIC still definitely doesn't seem useable, but the topic of the post appears to have resolved.Thank you for your reply, Steve!
-
Hmm, that's odd behaviour. It is possible for a NIC to become 'stuck'. If the OS configures it in such a way it becomes unresponsive it can remain that way until it's reinitialized by a complete power cycle. I'm not sure I've ever seen that on an em NIC though.
