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

    pfSense taking too long to reconnect after ISP hang

    Scheduled Pinned Locked Moved General pfSense Questions
    1 Posts 1 Posters 198 Views 1 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.
    • S Offline
      shoemakerleopard
      last edited by

      Hi guys! I'm having an issue with pfSense that's driving me crazy. My current architecture is:
      ISP's modem > pfSense > Switch/AP. The pfSense has static IPs assigned both on the WAN (186.31.162.4) & LAN (192.168.1.1) interfaces. The default ISP gateway is 186.31.162.1. The dns are 1.1.1.1 and 1.0.0.1.

      When using the pfSense I get frequent cuts of service of about 5 minutes. I tried replacing the pfSense with a simple TPLink router and I dont experience this cuts. Looking at the logs of system.log I see that the WAN interface goes down and then comes back up 4 seconds later. In the logs you can see that the interface goes down at 21:39:56 and comes back at 22:40:00. However, the pfSense takes about 5 minutes to restart normal service. The internet access however doesn't return until 21:43:54, when the logs finish. I have the feeling that the TPLink simply doesn't change anything in those 4 seconds window and that's why I dont see any noticeable cut. I don't have any reliable way of monitoring this with the TPLink though.
      Here's the logs. I replaced the repeated lines for brevity. I'm thinking there might be a way of reducing the sensitivity of pfSense to changes in the interfaces.

      Mar 22 21:39:56 machine check_reload_status: Linkup starting re0
Mar 22 21:39:56 machine kernel: re0: link state changed to DOWN
Mar 22 21:39:57 machine php-fpm[9087]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:39:57 machine check_reload_status: Reloading filter
Mar 22 21:39:57 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:39:57 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
{MESSAGE REPEATED IN BETWEEN}
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine check_reload_status: Linkup starting re0
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:00 machine kernel: re0: link state changed to UP
Mar 22 21:40:01 machine php-fpm[90789]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:40:01 machine check_reload_status: rc.newwanip starting re0
Mar 22 21:40:01 machine check_reload_status: Reloading filter
Mar 22 21:40:02 machine php-fpm[11357]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Mar 22 21:40:02 machine php-fpm[11357]: /rc.newwanip: rc.newwanip: on (IP address: 186.31.162.4) (interface: WAN[wan]) (real interface: re0).
Mar 22 21:40:02 machine php-fpm[11357]: /rc.newwanip: The command '/sbin/route delete -host 1.1.1.1' returned exit code '1', the output was 'route: route has not been found delete host 1.1.1.1 fib 0: not in table'
Mar 22 21:40:02 machine php-fpm[11357]: /rc.newwanip: The command '/sbin/route delete -host 1.0.0.1' returned exit code '1', the output was 'route: route has not been found delete host 1.0.0.1 fib 0: not in table'
Mar 22 21:40:02 machine check_reload_status: Reloading filter
Mar 22 21:40:08 machine rc.gateway_alarm[86193]: >>> Gateway alarm: WANGW (Addr:186.31.162.1 Alarm:1 RTT:8.275ms RTTsd:1.449ms Loss:21%)
Mar 22 21:40:08 machine check_reload_status: updating dyndns WANGW
Mar 22 21:40:08 machine check_reload_status: Restarting ipsec tunnels
Mar 22 21:40:08 machine check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 22 21:40:08 machine check_reload_status: Reloading filter
Mar 22 21:40:30 machine check_reload_status: Linkup starting re0
Mar 22 21:40:30 machine kernel: re0: link state changed to DOWN
Mar 22 21:40:31 machine php-fpm[11357]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:40:31 machine check_reload_status: Reloading filter
Mar 22 21:40:31 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:32 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:32 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:40:32 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
{MESSAGE REPEATED IN BETWEEN}
Mar 22 21:41:16 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:17 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:17 machine sshd[15533]: user root login class  [preauth]
Mar 22 21:41:17 machine sshd[15533]: user root login class  [preauth]
Mar 22 21:41:17 machine sshd[15533]: user root login class  [preauth]
Mar 22 21:41:17 machine sshd[15533]: Accepted publickey for root from 192.168.1.100 port 55568 ssh2: RSA SHA256:lQd8/kfBK28LiM0ryg14cNDlSIFtsWxmfy9bLIg1+W8
Mar 22 21:41:18 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:19 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:19 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:20 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:41:21 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
{MESSAGE REPEATED IN BETWEEN}
Mar 22 21:42:05 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:05 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:05 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:05 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:05 machine check_reload_status: Linkup starting re0
Mar 22 21:42:05 machine kernel: re0: link state changed to UP
Mar 22 21:42:06 machine php-fpm[90789]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:42:06 machine check_reload_status: rc.newwanip starting re0
Mar 22 21:42:06 machine check_reload_status: Reloading filter
Mar 22 21:42:07 machine php-fpm[8250]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Mar 22 21:42:07 machine php-fpm[8250]: /rc.newwanip: rc.newwanip: on (IP address: 186.31.162.4) (interface: WAN[wan]) (real interface: re0).
Mar 22 21:42:07 machine php-fpm[8250]: /rc.newwanip: The command '/sbin/route delete -host 1.1.1.1' returned exit code '1', the output was 'route: route has not been found delete host 1.1.1.1 fib 0: not in table'
Mar 22 21:42:07 machine php-fpm[8250]: /rc.newwanip: The command '/sbin/route delete -host 1.0.0.1' returned exit code '1', the output was 'route: route has not been found delete host 1.0.0.1 fib 0: not in table'
Mar 22 21:42:07 machine check_reload_status: Reloading filter
Mar 22 21:42:19 machine check_reload_status: Linkup starting re0
Mar 22 21:42:19 machine kernel: re0: link state changed to DOWN
Mar 22 21:42:20 machine php-fpm[90789]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:42:20 machine check_reload_status: Reloading filter
Mar 22 21:42:21 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:21 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:21 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
{MESSAGE REPEATED IN BETWEEN}
Mar 22 21:42:33 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:33 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:34 machine kernel: arpresolve: can't allocate llinfo for 186.31.162.1 on re0
Mar 22 21:42:34 machine check_reload_status: Linkup starting re0
Mar 22 21:42:34 machine kernel: re0: link state changed to UP
Mar 22 21:42:35 machine php-fpm[62730]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (186.31.162.4 )
Mar 22 21:42:35 machine check_reload_status: rc.newwanip starting re0
Mar 22 21:42:35 machine check_reload_status: Reloading filter
Mar 22 21:42:36 machine php-fpm[9087]: /rc.newwanip: rc.newwanip: Info: starting on re0.
Mar 22 21:42:36 machine php-fpm[9087]: /rc.newwanip: rc.newwanip: on (IP address: 186.31.162.4) (interface: WAN[wan]) (real interface: re0).
Mar 22 21:42:36 machine php-fpm[9087]: /rc.newwanip: The command '/sbin/route delete -host 1.1.1.1' returned exit code '1', the output was 'route: route has not been found delete host 1.1.1.1 fib 0: not in table'
Mar 22 21:42:36 machine php-fpm[9087]: /rc.newwanip: The command '/sbin/route delete -host 1.0.0.1' returned exit code '1', the output was 'route: route has not been found delete host 1.0.0.1 fib 0: not in table'
Mar 22 21:42:36 machine check_reload_status: Reloading filter
Mar 22 21:43:54 machine rc.gateway_alarm[66702]: >>> Gateway alarm: WANGW (Addr:186.31.162.1 Alarm:0 RTT:8.461ms RTTsd:5.354ms Loss:5%)
Mar 22 21:43:54 machine check_reload_status: updating dyndns WANGW
Mar 22 21:43:54 machine check_reload_status: Restarting ipsec tunnels
Mar 22 21:43:54 machine check_reload_status: Restarting OpenVPN tunnels/interfaces
Mar 22 21:43:54 machine check_reload_status: Reloading filter
      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.