Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NIC Broadcom 57412 10Gb not recognized

    Scheduled Pinned Locked Moved Hardware
    20 Posts 6 Posters 6.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rivest1000 @Edouard Moreau
      last edited by

      @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)

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by stephenw10

        Get it from the FreeBSD 11.2 ISO image.

        Comment on the feature request if it works for you.

        Steve

        R 1 Reply Last reply Reply Quote 0
        • R
          rivest1000 @stephenw10
          last edited by

          @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?

          R 1 Reply Last reply Reply Quote 0
          • R
            rivest1000 @rivest1000
            last edited by

            @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

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              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

              E R 4 Replies Last reply Reply Quote 0
              • E
                Edouard Moreau @stephenw10
                last edited by

                @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.

                1 Reply Last reply Reply Quote 0
                • R
                  rivest1000 @stephenw10
                  last edited by

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • R
                    rivest1000 @stephenw10
                    last edited by

                    @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?

                    1 Reply Last reply Reply Quote 0
                    • R
                      rivest1000 @stephenw10
                      last edited by

                      @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?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        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

                        1 Reply Last reply Reply Quote 0
                        • viktor_gV
                          viktor_g Netgate
                          last edited by

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

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.