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

    Why don't the gateways update themselves?

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 1.6k 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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Ok so I am doing load balancing with pfsense 2.0

      Now, ok so if I unplug a modem or if one fails. And I check status gateways, it says offline, ok that's fine.

      But when it eventually goes backonline, it still says offline. I have to go to the routing part, and hit save, and then apply, then it wakes back up and says online.

      Why isn't this automated?

      1 Reply Last reply Reply Quote 0
      • E Offline
        eri--
        last edited by

        It should.
        Show me your system log?

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          @ermal:

          It should.
          Show me your system log?

          Mar 27 23:35:28	apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
          Mar 27 23:49:06	apinger: ALARM: OPT1(4.2.2.1) *** delay ***
          Mar 27 23:49:14	apinger: alarm canceled: OPT1(4.2.2.1) *** delay ***
          Mar 27 23:49:16	check_reload_status: reloading filter
          Mar 27 23:49:16	php: : MONITOR: OPT1 has high latency, removing from routing group
          Mar 27 23:49:24	check_reload_status: reloading filter
          Mar 28 00:14:14	apinger: ALARM: OPT1(4.2.2.1) *** delay ***
          Mar 28 00:14:22	apinger: alarm canceled: OPT1(4.2.2.1) *** delay ***
          Mar 28 00:14:24	check_reload_status: reloading filter
          Mar 28 00:14:24	php: : MONITOR: OPT1 has high latency, removing from routing group
          Mar 28 00:14:32	check_reload_status: reloading filter
          Mar 28 00:16:28	sshd[50078]: Accepted keyboard-interactive/pam for root from 192.168.1.244 port 17385 ssh2
          Mar 28 00:20:30	login: login on ttyv0 as root
          Mar 28 01:01:00	php: : DynDns: Running updatedns()
          Mar 28 01:01:00	php: : DynDns: updatedns() starting
          Mar 28 01:01:00	php: : DynDns: _detectChange() starting.
          Mar 28 01:01:00	php: : DynDns: _checkIP() starting.
          Mar 28 01:01:00	php: : DynDns debug information: 76.102.159.xxx extracted from local system.
          Mar 28 01:01:00	php: : DynDns: Current WAN IP: 76.102.159.xxx
          Mar 28 01:01:00	php: : DynDns: Cached IP: 76.102.159.224
          Mar 28 01:01:00	php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
          Mar 28 05:46:59	apinger: ALARM: WAN(76.102.152.1) *** delay ***
          Mar 28 05:47:09	check_reload_status: reloading filter
          Mar 28 05:47:09	php: : MONITOR: WAN has high latency, removing from routing group
          Mar 28 05:47:34	apinger: alarm canceled: WAN(76.102.152.1) *** delay ***
          Mar 28 05:47:44	check_reload_status: reloading filter
          Mar 28 06:58:47	apinger: ALARM: WAN(76.102.152.1) *** delay ***
          Mar 28 06:58:57	check_reload_status: reloading filter
          Mar 28 06:58:57	php: : MONITOR: WAN has high latency, removing from routing group
          Mar 28 06:59:15	apinger: alarm canceled: WAN(76.102.152.1) *** delay ***
          Mar 28 06:59:25	check_reload_status: reloading filter
          Mar 28 07:56:47	dhclient[59901]: DHCPREQUEST on em0 to 68.87.76.39 port 67
          Mar 28 07:56:47	dhclient[59901]: DHCPACK from 68.87.76.39
          Mar 28 07:56:47	dhclient: RENEW
          Mar 28 07:56:47	dhclient: Creating resolv.conf
          Mar 28 07:56:47	dhclient[59901]: bound to 76.102.159.224 -- renewal in 172800 seconds.
          Mar 28 09:41:29	dhclient[53425]: DHCPREQUEST on re0 to 68.87.76.39 port 67
          Mar 28 09:41:29	dhclient[53425]: DHCPACK from 68.87.76.39
          Mar 28 09:41:29	dhclient: RENEW
          Mar 28 09:41:29	dhclient: Creating resolv.conf
          Mar 28 09:41:29	dhclient[53425]: bound to 76.126.99.181 -- renewal in 172800 seconds.
          Mar 28 13:33:26	apinger: ALARM: OPT1(4.2.2.1) *** down ***
          Mar 28 13:33:36	check_reload_status: reloading filter
          Mar 28 13:33:36	php: : MONITOR: OPT1 has high latency, removing from routing group
          Mar 28 13:33:42	apinger: alarm canceled: OPT1(4.2.2.1) *** down ***
          Mar 28 13:33:52	check_reload_status: reloading filter
          Mar 28 14:47:12	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.118
          Mar 28 14:47:12	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.118
          Mar 28 16:59:38	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.244
          Mar 28 16:59:38	php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.244
          

          I don't think anything is important going on here.

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