H87N-WIFI interfaces not recognized
-
I'm setting up my first pfsense box, and I just purchased a Gigabyte H87N-WIFI motherboard which has 2 ethernet ports and a wifi card built in.
I'm having an issue as the installer is not recognizing any of the built in interfaces. I'm assuming I'll have to build drivers on a working FreeBSD 8.3 system for these, and then copy them over, but I was wondering if anyone had done this and could offer any pointers?
I haven't seen any docs on how to do this specifically, but if someone can point out something I'm missing that would be awesome.
-
See: https://forum.pfsense.org/index.php/topic,70485.0.html
There are newer drivers that will support the Intel i217 NIC.
The Atheros NIC is an unknown quantity.
The wireless card is almost certainly completely unsupported by FreeeBSD and hence pfSense. :(Steve
-
Yup, just bought Gigabyte H87N-WiFi and install the latest pfsense 2.1.1.
Intel i217 NIC were detected but not for Atheros Gbe NIC :-[ and also the internal Wifi minicard.
Hope an update release supporting at least the Atheros Gbe NIC will come soon.
-
Try on of the 2.2 snapshots to see if the FreeBSD 10 drivers support the Atheros NIC. Those snapshots are still 'highly experimental' though. ;)
Steve
-
Just tried snapshot 2.2 alpha. Still not recognized the atheros Gbe NIC and the wireless card. :-[
-
Can you get the PCI vendor and device IDs for it? Perhaps there is an experimental driver for it.
Steve
-
I have the same issue with this board…not able to install 2.1 on it (i guess because i use ssd for appliance)
-
Using an SSD should not cause any problems with installation.
Steve
-
you have to manually install the drivers for it, and you should compile on the latest stable freebsd. I have one of these boards, its actually what im working on setting up today. There is a post on here somewhere with a aetheros driver that's been compiled that should work.
prolly mabe make a youtube how to on it.
-
The driver is now In FreeBSD:
https://github.com/markjdb/alx-freebsd/blob/master/README
It may be in pfSense 2.2 already, have you tried it?The driver is in 10 stable but not 10.1 which I believe 2.2 is built on.
Steve