Onboard NIC does not appear in pfSense

stephenw10

If it's appearing as re0 then the driver is correctly attaching to it. It should be available.
Could we see the output of 'ifconfig'.

Steve

wallabybob

A nic might not appear in pfSense because
1. It is not recognised by any device driver in the FreeBSD kernel (in which case it won't appear in the ifconfig output); or
2. It hasn't been added to the pool of interfaces used by pfSense. To do that go to Interfaces -> (assign) and click on the "+" button on the bottom right of the page. If there is no "+" button then pfSense has all the recognised interfaces.

netsysadmin

1. Output of 'ifconfig':

$ ifconfig
re1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
	options=389b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 90:94:e4:5f:75:06
	inet 192.168.6.207 netmask 0xffffff00 broadcast 192.168.6.255
	inet6 fe80::9294:e4ff:fe5f:7506%re1 prefixlen 64 scopeid 0x1 
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
re2: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=389b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 90:94:e4:5f:75:0e
	inet6 fe80::9294:e4ff:fe5f:750e%re2 prefixlen 64 scopeid 0x2 
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
pfsync0: flags=0<> metric 0 mtu 1460
	syncpeer: 224.0.0.240 maxupd: 128 syncok: 1
enc0: flags=41 <up,running>metric 0 mtu 1536
lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
	options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 
	nd6 options=43 <performnud,accept_rtadv>pflog0: flags=100 <promisc>metric 0 mtu 33664
re2_vlan60: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=3 <rxcsum,txcsum>ether 90:94:e4:5f:75:0e
	inet6 fe80::9294:e4ff:fe5f:7506%re2_vlan60 prefixlen 64 scopeid 0x7 
	inet 10.60.0.2 netmask 0xffff0000 broadcast 10.60.255.255
	inet A.B.C.57 netmask 0xfffffff8 broadcast A.B.C.63
	inet A.B.C.58 netmask 0xfffffff8 broadcast A.B.C.63
	inet A.B.C.59 netmask 0xfffffff8 broadcast A.B.C.63
	inet A.B.C.60 netmask 0xfffffff8 broadcast A.B.C.63
	inet A.B.C.61 netmask 0xfffffff8 broadcast A.B.C.63
	inet A.B.C.62 netmask 0xfffffff8 broadcast A.B.C.63
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	vlan: 60 parent interface: re2
re2_vlan61: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=3 <rxcsum,txcsum>ether 90:94:e4:5f:75:0e
	inet6 fe80::9294:e4ff:fe5f:7506%re2_vlan61 prefixlen 64 scopeid 0x8 
	inet 192.168.4.100 netmask 0xffffff00 broadcast 192.168.4.255
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	vlan: 61 parent interface: re2
re2_vlan62: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	options=3 <rxcsum,txcsum>ether 90:94:e4:5f:75:0e
	inet6 fe80::9294:e4ff:fe5f:7506%re2_vlan62 prefixlen 64 scopeid 0x9 
	inet 192.168.5.100 netmask 0xffffff00 broadcast 192.168.5.255
	nd6 options=43 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	vlan: 62 parent interface: re2</full-duplex></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></promisc></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></up,running></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,promisc,simplex,multicast>

2. There is no "+", so I guess pfSense has not recognised the onboard NIC.

I remember the mainboard (GIGABYTE) box mentioned that there are drivers for FreeBSD on the CD included.
Is it possible to install these drivers in pfSense?
Is there any risk?

Thanks again.

stephenw10

Hmm, well that's an interesting situation. The driver has clearly attached to the card since re0 is taken but it is not available as an interface. I would look through the boot log for some indication of what's happening here.

Steve

jimp

For certain really broken chips it's possible that the driver latched onto the card but couldn't fully initialize everything it needs on the phy.

the output of "pciconf -lvb" and the contents of /var/log/dmesg.boot would be the best thing to look at.

netsysadmin

I have attached the files.
What conclusion can you draw?

Thanks.

pciconf.txt
dmesg.boot.txt

jimp

re0: Unknown H/W revision: 0x2c800000

I'd say it's just a chip variant that the driver doesn't fully recognize. Try a 2.1 snapshot.

netsysadmin

OK. Thanks. Will try that.
However, as I mentioned in a post before in this thread: the drivers for the mainboard (GIGABYTE) include those for FreeBSD.
Is it possible to install these drivers in pfSense?
Is there any risk?

Thanks

stephenw10

It's almost certainly not possible. Any driver would have to be for FreeBSD 8.1 and would have to be a compiled kernel module as there are no build tools in pfSense.
If you really don't want to use 2.1 you could try this driver:
http://forum.pfsense.org/index.php/topic,58150.0.html

Steve

netsysadmin

I confirm that the driver is correctly loaded in 2.1BETA.
We do intend to switch to 2.1BETA very soon.

Thanks for all your help.