NIC Broadcom 57412 10Gb not recognized

Edouard Moreau

@grimson You're right. But this driver is supposed to already be part of pfSense, as Steve stated.

Grimson

@edouard-moreau said in NIC Broadcom 57412 10Gb not recognized:

@grimson You're right. But this driver is supposed to already be part of pfSense, as Steve stated.

Then open a bug report on redmine.

stephenw10

Whilst the driver is in the codebase it does not look like it's being built:

[2.4.5-DEVELOPMENT][admin@5100.stevew.lan]/root: kldstat -v | grep bnxt
[2.4.5-DEVELOPMENT][admin@5100.stevew.lan]/root:

So, yes, open that as a feature request on redmine to get it added.

Steve

Edouard Moreau

Feature request created : https://redmine.pfsense.org/issues/9155

rivest1000

@Edouard-Moreau Can you please send me a link for the if_bnxt.ko driver? I having the same problem with Broadcom 57412 Dual Port 10GbE SFP+.

[2.4.4-RELEASE][admin@pfSense.localdomain]/root: dmesg | grep eth
pci6: <network, ethernet> at device 0.0 (no driver attached)
pci6: <network, ethernet> at device 0.1 (no driver attached)
pci6: <network, ethernet> at device 0.0 (no driver attached)
pci6: <network, ethernet> at device 0.1 (no driver attached)

stephenw10

Get it from the FreeBSD 11.2 ISO image.

Comment on the feature request if it works for you.

Steve

rivest1000

@stephenw10 I simply copied the file via scp and ran kldload ./if_bnxt.ko ; is that all I need to do? Do you mind sending instructions?

I do see it now with kldstat :

/root: kldstat -v | grep bnxt
3 1 0xffffffff83223000 15b38 if_bnxt.ko (./if_bnxt.ko)
659 pci/bnxt

just reboot?

rivest1000

@rivest1000 Oh I guess I don't need a reboot :) :

bnxt0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether b0:26:28:24:eb:e0
hwaddr b0:26:28:24:eb:e0
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
status: active
bnxt1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
ether b0:26:28:24:eb:e1
hwaddr b0:26:28:24:eb:e1
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-SR <full-duplex,rxpause,txpause>)
status: active

stephenw10

Yup, you should just be able to kldload it like that. Put the kernel module in /boot/modules and then add the line if_bnxt_load="YES" to /boot/loader.conf.local so that it loads correctly at boot.

Steve

Edouard Moreau

@stephenw10
I'm glad that you were able to get your nic working, but please comment on the feature request at https://redmine.pfsense.org/issues/9155. It would be much more confortable not to have to use the workaround every major update.

rivest1000

@stephenw10 Is there still an issue with pinging IPs on these interfaces? I got the to come up, but no ping after configuring same IPs that were on the 1G nics.

rivest1000

@stephenw10 I can get the nic to ping for about 5 minutes and then dies. Cannot ping out or in. It also doesn't seem to work with a tagged Vlan at all :(. Is this a driver issue?

rivest1000

@stephenw10 I believe I figured it out. It was not pinging when I made a vlan tag. I had to run "ifconfig bnxt0 promisc". how can I force it to stay promisc on reboot? and is it safe to leave promisc on in production environment?

stephenw10

Usually that's no problem. You can use a shellcmd to put the NIC promiscuous mode.

You should probably try disabling any hw vlan tagging on the NIC too. That may be the cause there.

Steve

viktor_g

now in 2.5:
https://redmine.pfsense.org/issues/9155#note-7