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

    WAN is dropping out. Don't know what to do.

    Scheduled Pinned Locked Moved General pfSense Questions
    14 Posts 6 Posters 2.1k 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.
    • C
      cristi_gh
      last edited by

      WAN port is configured with a static IP. Nothing fancy. Standard stuff.
      WAN interface status was UP. Even so, no outside access.
      Logs, is there a way to activate a more verbose logging for this issue?

      1 Reply Last reply Reply Quote 0
      • A
        AndrewZ
        last edited by

        @cristi_gh:

        WAN interface status was UP. Even so, no outside access.

        Any errors in Status/Interfaces/WAN ?
        When "no internet":

        • Can you ping the next hop from the router?
        • Do you see an ARP entry for the next hop device?
        1 Reply Last reply Reply Quote 0
        • C
          cristi_gh
          last edited by

          I'll check tomorrow.
          I reinstalled everything over the weekend, fresh install + openvpn. I used the connection from home and loaded it pretty good. All weekend it's been working great. 30 minutes into the working hours today and the wan dropped. I had to default to the Linksys router. What the hell? How does pfsense crash and Linksys home router still works, I  don't know.
          I'll check the logs, and tomorrow I'll make some more tests including what you recommended.

          1 Reply Last reply Reply Quote 0
          • C
            cristi_gh
            last edited by

            I checked the logs and I see some activity, maybe someone has any clues?
            might be some gear in the network that's causing this.
            sample logs, they are larger in the attached files

            kernel

            Aug  5 17:40:52 192.168.0.1 kernel: tun1: changing name to 'ovpns1'
Aug  5 17:40:52 192.168.0.1 kernel: ovpns1: link state changed to UP
Aug  5 17:50:47 192.168.0.1 kernel: 
Aug  5 17:50:47 192.168.0.1 kernel: pfSense is now shutting down ...
Aug  5 17:50:47 192.168.0.1 kernel: 
Aug  5 17:52:05 192.168.0.1 kernel: re0: link state changed to UP
Aug  5 17:52:06 192.168.0.1 kernel: done.
Aug  5 17:52:06 192.168.0.1 kernel: Synchronizing user settings...
Aug  5 17:52:08 192.168.0.1 kernel: done.
Aug  5 17:52:08 192.168.0.1 kernel: Starting webConfigurator...
Aug  5 17:52:09 192.168.0.1 kernel: done.
Aug  5 17:52:09 192.168.0.1 kernel: Configuring CRON...done.
Aug  5 17:52:09 192.168.0.1 kernel: Starting NTP time client...done.
Aug  5 17:52:09 192.168.0.1 kernel: done.
Aug  5 17:52:09 192.168.0.1 kernel: Starting DHCPv6 service...done.
Aug  5 17:52:09 192.168.0.1 kernel: Configuring firewall.....
Aug  5 17:52:10 192.168.0.1 kernel: .done.
Aug  5 17:52:14 192.168.0.1 kernel: Generating RRD graphs...
Aug  5 17:52:15 192.168.0.1 kernel: done.
Aug  5 17:52:15 192.168.0.1 syslogd: kernel boot file is /boot/kernel/kernel
Aug  5 17:52:15 192.168.0.1 kernel: Starting syslog...done.
Aug  5 17:52:15 192.168.0.1 kernel: Starting CRON... 
Aug  5 17:52:15 192.168.0.1 kernel: done.
Aug  5 17:52:15 192.168.0.1 kernel: Starting package snort...done.
Aug  5 17:52:15 192.168.0.1 kernel: Starting package OpenVPN Client Export Utility...done.
Aug  5 17:52:16 192.168.0.1 kernel: pfSense (pfSense) 2.3.4-RELEASE (Patch 1) amd64 Fri Jul 14 14:52:43 CDT 2017
Aug  5 17:52:16 192.168.0.1 kernel: Bootup complete
Aug  7 08:30:45 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 08:30:45 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 08:30:49 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 09:03:27 192.168.0.1 kernel: arp: 192.168.0.101 moved from xx:xx:xx:xx:xx:xx to xx:xx:xx:xx:xx:xx on re0
Aug  7 09:30:59 192.168.0.1 kernel: arp: 192.168.0.101 moved from xx:xx:xx:xx:xx:xx to xx:xx:xx:xx:xx:xx on re0
Aug  7 09:49:16 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 09:49:16 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 09:49:20 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:00:00 192.168.0.1 kernel: arp: 192.168.0.101 moved from xx:xx:xx:xx:xx:xx to xx:xx:xx:xx:xx:xx on re0
Aug  7 10:24:30 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:24:30 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:24:34 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:26:17 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:26:17 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:26:21 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:26:32 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:26:32 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:26:36 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:26:43 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:26:43 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:26:47 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:26:54 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:26:54 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:26:58 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:27:03 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:27:03 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:27:07 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:27:12 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:27:12 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:27:16 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:27:21 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:27:21 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:27:25 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:27:30 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:27:30 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:27:34 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:29:30 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:29:30 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:29:34 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:31:48 192.168.0.1 kernel: re1: watchdog timeout
Aug  7 10:31:48 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:31:52 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:34:52 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:34:56 192.168.0.1 kernel: re1: watchdog timeout


            Aug  7 10:29:35 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:35 192.168.0.1 dhcpd: reuse_lease: lease age 127 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:35 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:35 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:36 192.168.0.1 dhcpd: reuse_lease: lease age 672 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.195
Aug  7 10:29:36 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.195 from xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:36 192.168.0.1 dhcpd: DHCPACK on 192.168.0.195 to xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:37 192.168.0.1 dhcpd: reuse_lease: lease age 627 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:29:37 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:37 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:37 192.168.0.1 dhcpd: reuse_lease: lease age 627 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:29:37 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.150 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:37 192.168.0.1 dhcpd: DHCPACK on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:40 192.168.0.1 dhcpd: reuse_lease: lease age 132 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:40 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:40 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:40 192.168.0.1 dhcpd: reuse_lease: lease age 132 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:40 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:40 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:41 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.51 from xx:xx:xx:xx:xx:xx via re0: unknown lease 192.168.0.51.
Aug  7 10:29:45 192.168.0.1 dhcpd: reuse_lease: lease age 681 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.195
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.195 from xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPACK on 192.168.0.195 to xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:45 192.168.0.1 dhcpd: reuse_lease: lease age 137 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:45 192.168.0.1 dhcpd: reuse_lease: lease age 137 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:45 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:50 192.168.0.1 dhcpd: reuse_lease: lease age 142 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:50 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:50 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:51 192.168.0.1 dhcpd: reuse_lease: lease age 143 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:51 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:51 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:51 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.51 from xx:xx:xx:xx:xx:xx via re0: unknown lease 192.168.0.51.
Aug  7 10:29:52 192.168.0.1 dhcpd: DHCPDISCOVER from xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:52 192.168.0.1 dhcpd: reuse_lease: lease age 642 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:29:52 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:52 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:52 192.168.0.1 dhcpd: reuse_lease: lease age 642 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:29:52 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.150 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:52 192.168.0.1 dhcpd: DHCPACK on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:53 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.157 to xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:54 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.157 (192.168.0.1) from xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:54 192.168.0.1 dhcpd: DHCPACK on 192.168.0.157 to xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:54 192.168.0.1 dhcpd: DHCPINFORM from 192.168.0.147 via re0
Aug  7 10:29:54 192.168.0.1 dhcpd: DHCPACK to 192.168.0.147 ( xx:xx:xx:xx:xx:xx) via re0
Aug  7 10:29:55 192.168.0.1 dhcpd: reuse_lease: lease age 691 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.195
Aug  7 10:29:55 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.195 from xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:55 192.168.0.1 dhcpd: DHCPACK on 192.168.0.195 to xx:xx:xx:xx:xx:xx via re0
Aug  7 10:29:56 192.168.0.1 dhcpd: reuse_lease: lease age 148 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:56 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:56 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:56 192.168.0.1 dhcpd: reuse_lease: lease age 148 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:29:56 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:56 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:29:59 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.51 from xx:xx:xx:xx:xx:xx via re0: unknown lease 192.168.0.51.
Aug  7 10:30:01 192.168.0.1 dhcpd: reuse_lease: lease age 153 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:30:01 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:01 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:01 192.168.0.1 dhcpd: reuse_lease: lease age 153 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:30:01 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:01 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:06 192.168.0.1 dhcpd: reuse_lease: lease age 158 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:30:06 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:06 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:06 192.168.0.1 dhcpd: reuse_lease: lease age 158 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100
Aug  7 10:30:06 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.100 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:06 192.168.0.1 dhcpd: DHCPACK on 192.168.0.100 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:07 192.168.0.1 dhcpd: reuse_lease: lease age 657 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:30:07 192.168.0.1 dhcpd: DHCPDISCOVER from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:07 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:07 192.168.0.1 dhcpd: reuse_lease: lease age 657 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.150
Aug  7 10:30:07 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.150 (192.168.0.1) from  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:07 192.168.0.1 dhcpd: DHCPACK on 192.168.0.150 to  xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:08 192.168.0.1 dhcpd: reuse_lease: lease age 704 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.195
Aug  7 10:30:08 192.168.0.1 dhcpd: DHCPREQUEST for 192.168.0.195 from xx:xx:xx:xx:xx:xx via re0
Aug  7 10:30:08 192.168.0.1 dhcpd: DHCPACK on 192.168.0.195 to xx:xx:xx:xx:xx:xx via re0
Aug  7 10:30:11 192.168.0.1 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Aug  7 10:30:11 192.168.0.1 dhcpd: Config file: /etc/dhcpd.conf
Aug  7 10:30:11 192.168.0.1 dhcpd: Database file: /var/db/dhcpd.leases
Aug  7 10:30:11 192.168.0.1 dhcpd: PID file: /var/run/dhcpd.pid
Aug  7 10:30:11 192.168.0.1 dhcpd: Internet Systems Consortium DHCP Server 4.3.5
Aug  7 10:30:11 192.168.0.1 dhcpd: Copyright 2004-2016 Internet Systems Consortium.
Aug  7 10:30:11 192.168.0.1 dhcpd: All rights reserved.
Aug  7 10:30:11 192.168.0.1 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Aug  7 10:30:11 192.168.0.1 dhcpd: Wrote 0 deleted host decls to leases file.
Aug  7 10:30:11 192.168.0.1 dhcpd: Wrote 0 new dynamic host decls to leases file.
Aug  7 10:30:11 192.168.0.1 dhcpd: Wrote 71 leases to leases file.
Aug  7 10:30:11 192.168.0.1 dhcpd: Listening on BPF/re0/ xx:xx:xx:xx:xx:xx/192.168.0.0/24
Aug  7 10:30:11 192.168.0.1 dhcpd: Sending on   BPF/re0/ xx:xx:xx:xx:xx:xx/192.168.0.0/24
Aug  7 10:30:11 192.168.0.1 dhcpd: Sending on   Socket/fallback/fallback-net
Aug  7 10:30:11 192.168.0.1 dhcpd: Server starting service.
Aug  7 10:30:11 192.168.0.1 dhcpd: reuse_lease: lease age 17 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.157
Aug  7 10:30:11 192.168.0.1 dhcpd: DHCPDISCOVER from xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:11 192.168.0.1 dhcpd: DHCPOFFER on 192.168.0.157 to xx:xx:xx:xx:xx:xx   via re0
Aug  7 10:30:12 192.168.0.1 dhcpd: reuse_lease: lease age 164 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.0.100

            dhcpd.txt
            unbound.txt
            rtsold.txt
            php-fpm.txt
            kernel.txt
            dpinger.txt
            dhcp6c.txt
            [check reload status.txt](/public/imported_attachments/1/check reload status.txt)

            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan
              last edited by

              I guess it boils  down to a "Realtec NIC" (re1) with difficulties. Swap it out for another one.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • F
                fredfox_uk
                last edited by

                Does look like an issue with the NIC. Maybe it's crapping out when large amounts of traffic are pushed through it?

                No surprise that a Realtek NIC is having problems.

                1 Reply Last reply Reply Quote 0
                • C
                  cristi_gh
                  last edited by

                  Great. I use a zotac ci323 nano, got it after reading reviews saying it's supported well, and plays nice.
                  Anyway, I did find the wan cable of a wifi router stuck into a LAN port on that wifi router. I guess that's what generated the noise (two dhcp servers in the same lan).
                  I'll wait and see what's what by tomorrow.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cristi_gh
                    last edited by

                    Still drops, twice a day. That's a lot for a 100 devices network.

                    While looking for the

                    Aug  7 10:31:52 192.168.0.1 kernel: re1: link state changed to UP
Aug  7 10:34:52 192.168.0.1 kernel: re1: link state changed to DOWN
Aug  7 10:34:56 192.168.0.1 kernel: re1: watchdog timeout

                    problem, I found some answers on opnsense forum:
                    https://forum.opnsense.org/index.php?topic=4183.msg17474#msg17474

                    It seems the new Realtek driver fixes this issue.
                    Any change on getting that to pfsense? Or is there anyone that could help me install it somehow? Seems to be the answer.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cristi_gh
                      last edited by

                      I think I solved the problem.
                      I found the Realtek 1.92 driver for the NIC, on another thread around here. So far no more kernel messages and no more WAN drop.
                      I'll attach the driver for further reference. Just remove the .txt extension, copy it to /boot/kernel, chmod 0555 and chown root:wheel on the file. Also add if_re_load="YES" to /boot/loader.conf. Check if the module is loaded with:

                      kldstat -v | grep if_re

                      if_re.ko.txt

                      1 Reply Last reply Reply Quote 0
                      • J
                        jtjaskot
                        last edited by

                        I know it hasn't quite been a week yet, but is your problem solved now?

                        1 Reply Last reply Reply Quote 0
                        • C
                          cristi_gh
                          last edited by

                          Yes, problem solved. It's been rock solid even since.
                          So it seems that the NIC driver was at fault, and v1.92 realtek driver fixes that problem.

                          1 Reply Last reply Reply Quote 0
                          • B
                            breakaway
                            last edited by

                            I've applied this fix to my Atom N3150 box with 2 x Realtek NICs. Before, when I would push a lot of traffic (600+ mbps) through the system, either the LAN or WAN interface (or both) would crash. None of the fixes I found on the internet including disabling hardware checksum / hardware offloading under Advanced fixed this.

                            But I'm happy to report that once I installed this driver, I can push a ton of traffic through the system without too much trouble!

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