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

    Network flapping

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 3 Posters 1.3k Views 3 Watching
    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.
    • X Offline
      xefil
      last edited by

      Hi all,
      I'm a happy pfSense user (CE) since many years.
      Now, since I've start using vlans on same ehternet, I'm noticing an issue I cannot understand very well.
      My pfSense is my WAN firewall (default gw), as well as DHCP server. Sometimes happens that I loose connection to the firewall and all my LAN stop to work. In the logs I can notice the following:

      Sep 29 10:04:21 pfSense check_reload_status[500]: Linkup starting re1
Sep 29 10:04:21 pfSense check_reload_status[500]: Linkup starting re1.10
Sep 29 10:04:21 pfSense check_reload_status[500]: Linkup starting re1.30
Sep 29 10:04:21 pfSense kernel: re1: watchdog timeout
Sep 29 10:04:21 pfSense kernel: re1: link state changed to DOWN
Sep 29 10:04:21 pfSense kernel: re1.10: link state changed to DOWN
Sep 29 10:04:21 pfSense kernel: re1.30: link state changed to DOWN
Sep 29 10:04:21 pfSense kernel: bridge0: link state changed to DOWN
Sep 29 10:04:22 pfSense php-fpm[63566]: /rc.linkup: Hotplug event detected for WIFILAN(opt2) static IP address (4: 192.168.3.1)
Sep 29 10:04:22 pfSense check_reload_status[500]: Reloading filter
Sep 29 10:04:22 pfSense php-fpm[10166]: /rc.linkup: Hotplug event detected for LAN(opt1) static IP address (4: 192.168.1.1)
Sep 29 10:04:22 pfSense php-fpm[10166]: /rc.linkup: DEVD Ethernet detached event for opt1
Sep 29 10:04:22 pfSense php-fpm[63566]: /rc.linkup: DEVD Ethernet detached event for opt2
Sep 29 10:04:23 pfSense php-fpm[63566]: /rc.linkup: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1759133063] unbound[88180:0] error: bind: address already in use [1759133063] unbound[88180:0] fatal error: could not open ports'
Sep 29 10:04:24 pfSense check_reload_status[500]: Linkup starting re1
Sep 29 10:04:24 pfSense check_reload_status[500]: Linkup starting re1.10
Sep 29 10:04:24 pfSense check_reload_status[500]: Linkup starting re1.30
Sep 29 10:04:24 pfSense kernel: re1: link state changed to UP
Sep 29 10:04:24 pfSense kernel: re1.10: link state changed to UP
Sep 29 10:04:24 pfSense kernel: re1.30: link state changed to UP
Sep 29 10:04:24 pfSense kernel: bridge0: link state changed to UP
Sep 29 10:04:24 pfSense php-fpm[63566]: /rc.linkup: The command '/sbin/ifconfig 'ath0_wlan1' -staticarp ' returned exit code '1', the output was 'ifconfig: interface ath0_wlan1 does not exist'
Sep 29 10:04:24 pfSense php-fpm[63566]: /rc.linkup: The command '/usr/sbin/arp -d -i 'ath0_wlan1' -a > /dev/null 2>&1 ' returned exit code '1', the output was ''
Sep 29 10:04:24 pfSense check_reload_status[500]: Reloading filter
Sep 29 10:04:25 pfSense php-fpm[441]: /rc.linkup: Hotplug event detected for WIFILAN(opt2) static IP address (4: 192.168.3.1)
Sep 29 10:04:25 pfSense check_reload_status[500]: Reloading filter
Sep 29 10:04:25 pfSense php-fpm[441]: /rc.linkup: DEVD Ethernet attached event for opt2
Sep 29 10:04:25 pfSense php-fpm[441]: /rc.linkup: HOTPLUG: Triggering address refresh on opt2 (re1.30)
Sep 29 10:04:25 pfSense check_reload_status[500]: rc.newwanip starting re1.30
Sep 29 10:04:25 pfSense php-fpm[10166]: /rc.linkup: The command '/sbin/ifconfig 'ath0_wlan1' -staticarp ' returned exit code '1', the output was 'ifconfig: interface ath0_wlan1 does not exist'
Sep 29 10:04:25 pfSense php-fpm[10166]: /rc.linkup: The command '/usr/sbin/arp -d -i 'ath0_wlan1' -a > /dev/null 2>&1 ' returned exit code '1', the output was ''
Sep 29 10:04:25 pfSense php-fpm[62484]: /rc.linkup: Hotplug event detected for LAN(opt1) static IP address (4: 192.168.1.1)
Sep 29 10:04:25 pfSense php-fpm[62484]: /rc.linkup: DEVD Ethernet attached event for opt1
Sep 29 10:04:25 pfSense php-fpm[62484]: /rc.linkup: HOTPLUG: Triggering address refresh on opt1 (re1.10)
Sep 29 10:04:25 pfSense check_reload_status[500]: rc.newwanip starting re1.10
Sep 29 10:04:26 pfSense php-fpm[440]: /rc.newwanip: rc.newwanip: Info: starting on re1.30.
Sep 29 10:04:26 pfSense php-fpm[440]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.3.1) (interface: WIFILAN[opt2]) (real interface: re1.30).
Sep 29 10:04:26 pfSense php-fpm[62484]: /rc.newwanip: rc.newwanip: Info: starting on re1.10.
Sep 29 10:04:26 pfSense php-fpm[62484]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.1.1) (interface: LAN[opt1]) (real interface: re1.10).
Sep 29 10:04:27 pfSense php-fpm[440]: /rc.newwanip: Gateway, NONE AVAILABLE
Sep 29 10:04:27 pfSense php-fpm[62484]: /rc.newwanip: Gateway, NONE AVAILABLE
Sep 29 10:04:29 pfSense php-fpm[62484]: /rc.newwanip: The command '/sbin/ifconfig 'ath0_wlan1' -staticarp ' returned exit code '1', the output was 'ifconfig: interface ath0_wlan1 does not exist'
Sep 29 10:04:29 pfSense php-fpm[62484]: /rc.newwanip: The command '/usr/sbin/arp -d -i 'ath0_wlan1' -a > /dev/null 2>&1 ' returned exit code '1', the output was ''
Sep 29 10:04:29 pfSense php-fpm[62484]: /rc.newwanip: Resyncing OpenVPN instances for interface LAN.
Sep 29 10:04:29 pfSense php-fpm[62484]: /rc.newwanip: Creating rrd update script
Sep 29 10:04:31 pfSense php-fpm[62484]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 192.168.1.1 ->  192.168.1.1 - Restarting packages.
Sep 29 10:04:31 pfSense check_reload_status[500]: Starting packages
Sep 29 10:04:31 pfSense check_reload_status[500]: Reloading filter
Sep 29 10:04:32 pfSense php-fpm[441]: /rc.start_packages: Restarting/Starting all packages.
Sep 29 10:04:32 pfSense php-fpm[441]: /rc.start_packages: Configuration Change: (system): pfBlockerNG: saving DNSBL changes
Sep 29 10:04:32 pfSense check_reload_status[500]: Syncing firewall
Sep 29 10:04:32 pfSense bandwidthd[98048]: Monitoring subnet 192.168.4.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98048]: Monitoring subnet 192.168.1.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98048]: Monitoring subnet 192.168.3.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98048]: Monitoring subnet 192.168.2.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98095]: Monitoring subnet 192.168.4.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98095]: Monitoring subnet 192.168.1.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98095]: Monitoring subnet 192.168.3.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[98095]: Monitoring subnet 192.168.2.0 with netmask 255.255.255.0
Sep 29 10:04:32 pfSense bandwidthd[99826]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[99700]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[99943]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[24]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[99826]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[99943]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[99700]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[24]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[552]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[824]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[246]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[908]: Opening re1.10
Sep 29 10:04:32 pfSense bandwidthd[552]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[824]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[908]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense bandwidthd[246]: Packet Encoding: Ethernet
Sep 29 10:04:32 pfSense tail_pfb[1971]: [pfBlockerNG] Firewall Filter Service stopped
Sep 29 10:04:32 pfSense php_pfb[2581]: [pfBlockerNG] filterlog daemon stopped
Sep 29 10:04:32 pfSense tail_pfb[6349]: [pfBlockerNG] Firewall Filter Service started
Sep 29 10:04:32 pfSense php_pfb[6678]: [pfBlockerNG] filterlog daemon started
Sep 29 10:04:37 pfSense kernel: re1: watchdog timeout
Sep 29 10:04:37 pfSense kernel: re1: link state changed to DOWN
Sep 29 10:04:37 pfSense kernel: re1.10: link state changed to DOWN
Sep 29 10:04:37 pfSense kernel: re1.30: link state changed to DOWN
Sep 29 10:04:37 pfSense kernel: bridge0: link state changed to DOWN

      Seems the port is flapping, but the switch is not reporting useful informations.
      I've reset today CRC counters on the switch. On pfSense no sensible CRC found.

      Suggestions?
      A way to watch deeper in the issue?

      Thanks!
      Simon

      fireodoF 1 Reply Last reply Reply Quote 0
      • fireodoF Offline
        fireodo @xefil
        last edited by

        @xefil said in Network flapping:

        Suggestions?
        A way to watch deeper in the issue?

        Hi,

        AFAIK Realtek NICs are susceptible for strange behaviour so keep an eye on the Realtek driver to be updated to the recent version according your pfsense version. (you didnt specified that)

        my 2 cents,
        fireodo

        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
        pfsense 2.8.1 CE
        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

        1 Reply Last reply Reply Quote 0
        • X Offline
          xefil
          last edited by

          Thanks @fireodo !
          You're right, haven't specified any inf about the version I have:

          BIOS
          Vendor: American Megatrends Inc.
          Version: 5.12
          Release Date: Tue Nov 10 2020
          Boot Method: UEFI
          Version
          2.8.0-RELEASE (amd64)
          built on Tue Sep 9 17:24:00 CEST 2025
          FreeBSD 15.0-CURRENT
          CPU Type
          Intel(R) Xeon(R) CPU E3-1535M v6 @ 3.10GHz
          Current: 3294 MHz, Max: 3100 MHz
          8 CPUs : 1 package(s) x 4 core(s) x 2 hardware threads
          AES-NI CPU Crypto: Yes (active)
          QAT Crypto: No

          About realtek drivers, is there a way to update the manually or it's all handled by the pfSense version?

          Thank you!

          Simon

          PS: I start having these issues on similar hardware on 2.7.x as well.

          fireodoF 2 Replies Last reply Reply Quote 0
          • fireodoF Offline
            fireodo @xefil
            last edited by fireodo

            @xefil said in Network flapping:

            About realtek drivers, is there a way to update the manually or it's all handled by the pfSense version?

            Yes there is a way to update manually (no pfsense is not handling that - pfsense uses the standard driver included in the kernel) - do these steps on the console:
            (this is on a 2.8.1 pfsenseCE)

            pkg search realtek

            you will get this answer:

            realtek-re-kmod-1100.00.1500029_1 Kernel driver for Realtek PCIe Ethernet Controllers

            then do a:

            pkg install realtek-re-kmod-1100.00.1500029_1

            After that you should add these lines to /boot/loader.conf.local (if you dont have it, create it)

            if_re_load=“YES”
if_re_name="/boot/modules/if_re.ko"

            after that a reboot is required. With

            kldstat

            you can verify if the driver is loaded.

            Good luck!

            Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
            SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
            pfsense 2.8.1 CE
            Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

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

              Yup that ^.

              If you see:
              kernel: re1: watchdog timeout
              You should use the alternative driver.

              1 Reply Last reply Reply Quote 0
              • fireodoF Offline
                fireodo @xefil
                last edited by

                @xefil said in Network flapping:

                2.8.0-RELEASE (amd64)

                PS. I would update to 2.8.1 before update the Realtek driver ... (just a kind suggestion)

                Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                pfsense 2.8.1 CE
                Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                1 Reply Last reply Reply Quote 1
                • X Offline
                  xefil
                  last edited by

                  Ok, I'll give a try to suggestions. If 2.8.1 doesn't include driver changes, I'll try updating them.
                  Thank you!
                  Simon

                  fireodoF 1 Reply Last reply Reply Quote 0
                  • fireodoF Offline
                    fireodo @xefil
                    last edited by

                    @xefil said in Network flapping:

                    Thank you!

                    Hope it helps! ☺

                    Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                    SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                    pfsense 2.8.1 CE
                    Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

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