PfSense not detecting PCI-E nic!
-
Hi!
Being relatively new to pfSense I've oriented myself before through virtualbox to learn the basics of the software. I've just had the opportunity to buy a used PC by a friend with only one NIC, so purchased TP-LINK PCI-E 1Gbit card for about $15 at the local store.
I had already prepared an USB drive with pfsense, continuing installing the NIC, fastened it with a screw. Started the pfSense installation from the usb and everything goes smoothly - up to the point where I have to assign the interfaces, it discovers the two onboard (one LAN and one WLAN) but not the TP-LINK.
Why?
I'm using the latest version of pfSense and I don't have a CD/DVD drive. The BIOS runs pretty much on default settings with the exception to boot the USB.
Edit:
I managed to find out that the card is an TG-3468, I suppose it's an v2 as the productimage screams "Rev 2.0". A fast google search implies the FreeBSD support is already there.
-
its in freebsd-current (something that might be in a future freebsd 12 or 13).
pfSense 2.3.x is based on freebsd 10.3 / pfSense 2.4(.x) will be based on freebsd 11(.x)realtek nics/chipsets should be avoided if possible anyhow.
best to get a nic with an intel chipset
-
its in freebsd-current (something that might be in a future freebsd 12 or 13).
pfSense 2.3.x is based on freebsd 10.3 / pfSense 2.4(.x) will be based on freebsd 11(.x)realtek nics/chipsets should be avoided if possible anyhow.
best to get a nic with an intel chipsetpfSense finds both onboard Realtek and Atheros (wlan), but not the TP-Link. But if I am to replace the NIC, is "Intel Pro/1000CT" a compatible alternative?
-
"Intel Pro/1000CT" is a good choice.
-
I have used TP-Link TG-3468 cards in three Pfs setups and they were always recognised. In all cases the motherboards were / are Gigabyte. So, I can confirm that the card should be recognised, perhaps it's damaged or there is a motherboard fault.
J
