Missing NIC driver "oce" in 2.1.5 / 2.2-RC
-
Hi all,
I'm trying to install pfSense on a new high performance machine equipped with a HP NC552SFP, this card is a rebranded Emulex BladeEngine 3 card (Dual Port 10 GB/s). According to the Hardware Compatibility List of FreeBSD this NIC is supported through the oce driver since FreeBSD 8.3.
This driver seems not to be included in the pfSense installation images (neither current 2.1.5 nor 2.2 RC), but the card works as expected when using the FreeBSD Live CD (tested with 10.1 which 2.2 RC is based on). Is there a way to install this driver onto the pfSense installation? Or am I missing something fundamental in the way pfSense incorporates the NIC drivers (they seem to be mainly directly included in the kernel and not as modules if I look at /boot/kernel/)?
Is it possible (and advised for production use) to build a new pfSense FreeBSD kernel and the needed module to get this card running? Or would I be better off copying the binary module from a FreeBSD machine matching release and architecture to the pfSense server and start this driver on boot through loader.conf?
Thanks in advance for any input,
Steelynose -
would I be better off copying the binary module from a FreeBSD machine matching release and architecture to the pfSense server and start this driver on boot through loader.conf?
I've done this back in the 2.0.3 era on a FitPC having some exotic realtek NIC, worked perfectly with module files. Done it with soundcard drivers too.
-
Yep. Grab a kernel module from the appropriate FreeBSD version. However that is clearly not a typical network card. Will it function with just a driver or does it need utilities to configure it?
Edit: the man page doesn't indicate you do.
Steve
-
Hello Guys,
I have an emulex OCE11102-NT which works well on freebsd 10.1. I get the oce driver from there and add it to pfsense which see my two 10Gbe ports. However, I can't make any vlan working with. It works well on pfsense but not directly on PFsense 2.2.2. I ran some tests with Emulex, it seems the VLAN tag received by the network card is not correct.
Any idea of what's going on ?
Thank you
