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

    Placa de rede para de funcionar

    Scheduled Pinned Locked Moved
    Hardware
    4
    25
    1.6k
    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.
    • F
      fcostars @stephenw10
      last edited by

      @stephenw10
      No, the onboard network card is the lan, the wan is on the off board.
      and it is precisely the off board that stops working.

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

        @fcostars said in Placa de rede para de funcionar:

        Hp Nc364t Hstns-bn26

        Hmm, that looks like an Intel i340 based NIC so I'd expect it to work fine.

        What do you see logged when it fails?

        1 Reply Last reply Reply Quote 0
        • F
          fcostars @fcostars
          last edited by

          @fcostars
          Sorry, I'll explain better.
          I have an onboar network card that works very well. The problem is with the off board network card with 4 ports and one of them stops working. This happens on all three pfsense servers

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

            Right so what exactly happens when it fails? What is logged?

            F 1 Reply Last reply Reply Quote 0
            • F
              fcostars @stephenw10
              last edited by

              @stephenw10
              the port continues down, I restart the gateway and nothing happens. I have to restart the entire server. It works again for a while after one of the ports goes down.

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

                Ok so the link actually goes down? Link LEDs on the NICs go out?

                What does ifconfig show?

                What is shown in the system log when this happens?

                F 1 Reply Last reply Reply Quote 0
                • F
                  fcostars @stephenw10
                  last edited by

                  @stephenw10
                  Sep 26 11:46:52 php-fpm 48006 /rc.filter_configure_sync: GW States: One or more gateways is down, flushing all states: ALGAR_PPPOE
                  Sep 26 11:46:54 ppp 77741 [opt2_link0] PPPoE connection timeout after 9 seconds
                  Sep 26 11:46:54 ppp 77741 [opt2_link0] Link: DOWN event
                  Sep 26 11:46:54 ppp 77741 [opt2_link0] LCP: Down event
                  Sep 26 11:46:54 ppp 77741 [opt2_link0] Link: reconnection attempt 1 in 2 seconds
                  Sep 26 11:46:55 check_reload_status 413 Linkup starting re1
                  Sep 26 11:46:55 kernel re1: watchdog timeout
                  Sep 26 11:46:55 kernel re1: link state changed to DOWN
                  Sep 26 11:46:56 ppp 77741 [opt2_link0] Link: reconnection attempt 1
                  Sep 26 11:46:56 ppp 77741 [opt2_link0] PPPoE: Connecting to ''
                  Sep 26 11:46:56 ppp 77741 caught fatal signal TERM
                  Sep 26 11:46:56 ppp 77741 [opt2] IFACE: Close event
                  Sep 26 11:46:56 ppp 77741 [opt2] IPCP: Close event
                  Sep 26 11:46:58 ppp 77741 [opt2] Bundle: Shutdown
                  Sep 26 11:46:58 ppp 77741 [opt2_link0] Link: Shutdown
                  Sep 26 11:46:58 kernel re1: link state changed to UP
                  Sep 26 11:46:58 check_reload_status 413 Linkup starting re1
                  Sep 26 11:46:58 ppp 77741 process 77741 terminated
                  Sep 26 11:46:58 check_reload_status 413 Reloading filter
                  Sep 26 11:46:59 ppp 94109 Multi-link PPP daemon for FreeBSD
                  Sep 26 11:46:59 ppp 94109 process 94109 started, version 5.9
                  Sep 26 11:46:59 ppp 94109 web: web is not running
                  Sep 26 11:46:59 ppp 94109 [opt2] Bundle: Interface ng0 created
                  Sep 26 11:46:59 ppp 94109 [opt2_link0] Link: OPEN event
                  Sep 26 11:46:59 kernel ng0: changing name to 'pppoe1'
                  Sep 26 11:46:59 ppp 94109 [opt2_link0] LCP: Open event
                  Sep 26 11:46:59 ppp 94109 [opt2_link0] LCP: state change Initial --> Starting
                  Sep 26 11:46:59 ppp 94109 [opt2_link0] LCP: LayerStart
                  Sep 26 11:46:59 ppp 94109 [opt2_link0] PPPoE: Connecting to ''
                  Sep 26 11:47:00 sshguard 45311 Exiting on signal.

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

                    @fcostars said in Placa de rede para de funcionar:

                    Sep 26 11:46:55 kernel re1: watchdog timeout
                    Sep 26 11:46:55 kernel re1: link state changed to DOWN

                    Ok you actually have a Realtek NIC and its hitting timeout events. Since that's re1 you must have at least two Realtek NICs.

                    What interface is re1 being used for? Is that the WAN?

                    Is that really an HP NC364T? Real NC364Ts use Intel 82571EB chips.

                    F 1 Reply Last reply Reply Quote 0
                    • F
                      fcostars @stephenw10
                      last edited by

                      @stephenw10
                      Sorry, is SE-LGI8111-4bt on this server.

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

                        @fcostars said in Placa de rede para de funcionar:

                        SE-LGI8111-4bt

                        Ok so the problem there is the Realtek NIC. It's better to avoid them when you can.

                        The only thing you can try there, other than replacing it, is to use the alternative realtek-kmod-driver:
                        At the command line run:
                        pkg install realtek-re-kmod
                        Then run:

                        echo 'if_re_load="YES"' >> /boot/loader.conf.local
echo 'if_re_name="/boot/modules/if_re.ko"' >> /boot/loader.conf.local

                        Then reboot and check the boot logs show the newer driver:

                        re0: <Realtek PCIe GbE Family Controller> port 0x1000-0x10ff mem 0xf7a00000-0xf7a00fff,0xf7900000-0xf7903fff irq 16 at device 0.0 on pci1
re0: Using Memory Mapping!
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: version:1.97.00
re0: Ethernet address: 00:0d:b9:38:30:10

                        steve

                        F 3 Replies Last reply Reply Quote 1
                        • F
                          fcostars @stephenw10
                          last edited by

                          @stephenw10
                          ok, I did as you instructed me!
                          this was the result

                          re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xe000-0xe0ff mem 0xf7b00000-0xf7b00fff,0xf0300000-0xf0303fff irq 17 at device 0.0 on pci4
                          re0: Using 1 MSI-X message
                          re0: Chip rev. 0x2c800000
                          re0: MAC rev. 0x00100000
                          miibus0: <MII bus> on re0
                          rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
                          rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
                          re0: Using defaults for TSO: 65518/35/2048
                          re0: Ethernet address: 00:e0:4c:68:20:25
                          re0: netmap queues/slots: TX 1/256, RX 1/256

                          Thank you very much!

                          Now I'll wait if there will be any problems.

                          1 Reply Last reply Reply Quote 0
                          • F
                            fcostars @stephenw10
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • PotapuchP
                              Potapuch
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • F
                                fcostars @stephenw10
                                last edited by

                                @stephenw10

                                Now it worked!

                                I added the lines in the conf.local file.
                                if_re_load="YES" >> /boot/loader.conf.local
                                if_re_name="/boot/modules/if_re.ko" >> /boot/loader.conf.local

                                re0: <Realtek PCIe GbE Family Controller> port 0xe000-0xe0ff mem 0xf7b00000-0xf7b00fff,0xf0300000-0xf0303fff irq 17 at device 0.0 on pci4
                                re0: Using Memory Mapping!
                                re0: Using 1 MSI-X message
                                re0: version:1.98.00
                                re0: Ethernet address: 00:e0:4c:68:20:25

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

                                  Nice. Yes you need to see the 'version:' logged to know it has loaded.

                                  See if that stops the timeouts.

                                  Steve

                                  F 2 Replies Last reply Reply Quote 1
                                  • F
                                    fcostars @stephenw10
                                    last edited by

                                    @stephenw10
                                    Thank you very much!

                                    1 Reply Last reply Reply Quote 1
                                    • F
                                      fcostars @stephenw10
                                      last edited by

                                      @stephenw10
                                      One last question.
                                      Which network card do you recommend buying?

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

                                        Something Intel based. Hence I didn't expect that HP card you referred to to be an issue. Any i350 NIC will be good. There are a lot of fake Intel NICs around though so be careful.

                                        F 1 Reply Last reply Reply Quote 0
                                        • F
                                          fcostars @stephenw10
                                          last edited by

                                          @stephenw10 Thank you!

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            sTicKs23
                                            last edited by sTicKs23

                                            I had the same problem with a Realtek onboard LAN for many years.
                                            64abf2b3-8aa9-4e3a-99e3-e705f72f8f73-image.png
                                            What actually worked for me, was to clone https://github.com/alexdupre/rtl_bsd_drv to a FreeBSD 14 instance (branch v1.98) and, compile the driver with make, backup the old if_re.ko from /boot/kernel, and copy the compiled driver over to /boot/kernel.
                                            c63e9fad-3952-46cf-bf20-4119ae81d448-image.png

                                            Already compiled driver if anyone is looking for it (zip pass 123): https://1drv.ms/u/s!AteTpjotrz-qiuMVNwFrD6CY72xSpg?e=Ftc6ui

                                            3b3a758b-5e98-4711-aed1-ce89b9bf3696-image.png

                                            1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post