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

    Reload loop - pfsense unuseable

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    13 Posts 3 Posters 3.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.
    • G
      ggzengel
      last edited by

      I downgraded to
      2.1-BETA1 (amd64)
      built on Sat Feb 2 01:46:53 EST 2013

      With this version I don't have this problem.
      If have 2 gateway groups with 3 wans inside and 1 wan (tier1 and tier5 in the groups) which is down.

      One group is used in openvpn.

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

        Try a newer snap?

        Though I would wait for one not dated Saturday as it has GW route issues, though nothing too major :P

        1 Reply Last reply Reply Quote 0
        • G
          ggzengel
          last edited by

          Meanwhile I updated to
          2.1-BETA1 (amd64)
          built on Sat Feb 9 23:46:16 EST 2013

          Every 15 sec it reload the filters and ipsec tunnels stop forwarding for a few seconds.

          It says:
          php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing

          But that's not true.

          Feb 10 15:01:08 pfsense-hd php: : Forcefully reloading IPsec racoon daemon
Feb 10 15:01:08 pfsense-hd php: : Forcefully reloading IPsec racoon daemon
Feb 10 15:01:23 pfsense-hd check_reload_status: Updating all dyndns
Feb 10 15:01:23 pfsense-hd check_reload_status: Restarting ipsec tunnels
Feb 10 15:01:23 pfsense-hd check_reload_status: Restarting OpenVPN tunnels/interfaces
Feb 10 15:01:23 pfsense-hd check_reload_status: Reloading filter
Feb 10 15:01:25 pfsense-hd php: : DynDns: updatedns() starting
Feb 10 15:01:25 pfsense-hd php: : DynDns debug information (): 78.42.74.173 extracted from local system.
Feb 10 15:01:25 pfsense-hd php: : DynDNS (): running get_failover_interface for opt1\. found em2
Feb 10 15:01:25 pfsense-hd php: : DynDns debug information (): 78.42.74.173 extracted from local system.
Feb 10 15:01:25 pfsense-hd php: : DynDns (): Current WAN IP: 78.42.74.173 Cached IP: 78.42.74.173
Feb 10 15:01:25 pfsense-hd php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 10 15:01:25 pfsense-hd kernel: ovpnc1: link state changed to DOWN
Feb 10 15:01:25 pfsense-hd php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Feb 10 15:01:25 pfsense-hd php: : The command '/sbin/route -q delete 10.255.255.2' returned exit code '1', the output was 'route: writing to routing socket: No such process'
Feb 10 15:01:25 pfsense-hd kernel: ovpnc1: link state changed to UP
Feb 10 15:01:25 pfsense-hd check_reload_status: rc.newwanip starting ovpnc1
Feb 10 15:01:25 pfsense-hd kernel: ovpnc2: link state changed to DOWN
Feb 10 15:01:25 pfsense-hd php: : The command '/sbin/route -q delete 10.255.255.130' returned exit code '1', the output was 'route: writing to routing socket: No such process'
Feb 10 15:01:25 pfsense-hd kernel: ovpnc2: link state changed to UP
Feb 10 15:01:25 pfsense-hd check_reload_status: rc.newwanip starting ovpnc2
Feb 10 15:01:26 pfsense-hd php: : DynDns: updatedns() starting
Feb 10 15:01:26 pfsense-hd php: : DynDns debug information (): 217.91.144.12 extracted from local system.
Feb 10 15:01:26 pfsense-hd php: : DynDNS (): running get_failover_interface for opt2\. found pppoe0
Feb 10 15:01:26 pfsense-hd php: : DynDns debug information (): 217.91.144.12 extracted from local system.
Feb 10 15:01:26 pfsense-hd php: : DynDns (): Current WAN IP: 217.91.144.12 Cached IP: 217.91.144.12
Feb 10 15:01:26 pfsense-hd php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Feb 10 15:01:27 pfsense-hd php: : rc.newwanip: Informational is starting ovpnc1.
Feb 10 15:01:27 pfsense-hd php: : rc.newwanip: on (IP address: 10.255.255.2) (interface: opt7) (real interface: ovpnc1).
Feb 10 15:01:27 pfsense-hd php: : Removing static route for monitor 194.25.2.129 and adding a new route through 217.0.117.215
Feb 10 15:01:28 pfsense-hd php: : rc.newwanip: Informational is starting ovpnc2.
Feb 10 15:01:28 pfsense-hd php: : rc.newwanip: on (IP address: 10.255.255.130) (interface: opt6) (real interface: ovpnc2).
Feb 10 15:01:28 pfsense-hd php: : Removing static route for monitor 194.25.2.129 and adding a new route through 217.0.117.215
Feb 10 15:01:33 pfsense-hd php: : Forcefully reloading IPsec racoon daemon
Feb 10 15:01:34 pfsense-hd php: : Forcefully reloading IPsec racoon daemon
          1 Reply Last reply Reply Quote 0
          • C
            cybercare
            last edited by

            hmm I don't see the VPN issue. I have a tunnel from an x86 box to an x64 box in a datacenter both now running the last Feb 09 build and the tunnel has been up since I updated which was a few hours ago.

            You using IP or name to make the connection? If the name maybe something is happening when it tries to re-resolve it or something silly.

            1 Reply Last reply Reply Quote 0
            • G
              ggzengel
              last edited by

              I think it's because one interface in the gateway group is down and the reload script is doing to much work.
              The second problem could be the openvpn client which didn't come up completely.

              I think if there are problems with some interfaces the router should work allways stable.

              1 Reply Last reply Reply Quote 0
              • G
                ggzengel
                last edited by

                sometimes I see:
                Feb 10 15:34:58 pfsense-hd php: : GATEWAYS: We did not find the first tier of the gateway group WAN! That's odd.
                Feb 10 15:34:58 pfsense-hd php: : Gateways status could not be determined, considering all as up/active. (Group: Internet)
                Feb 10 15:34:58 pfsense-hd php: : Gateways status could not be determined, considering all as up/active. (Group: WAN)

                I already removed and added the (disabled) wan interface on the group. The script should see the interface and know that it's down.

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

                  Can you share your configuration information.
                  Just the log does not tell anything about your architecture and guess work is hard for troubleshooting anything.

                  1 Reply Last reply Reply Quote 0
                  • G
                    ggzengel
                    last edited by

                    I will do this, but I need sometime for anonymization.
                    I wish there were an anonymization function at export.

                    1 Reply Last reply Reply Quote 0
                    • G
                      ggzengel
                      last edited by

                      @ermal: you got PM

                      1 Reply Last reply Reply Quote 0
                      • G
                        ggzengel
                        last edited by

                        I updated now my 4th pfsense from 1. Feb to 2.1-BETA1 (amd64) built on Fri Feb 15 04:33:17 EST 2013.
                        I have the same problem again.
                        If one interface unwired or for other reason down (gateway don't reply on ping) it reloads the config every 15 seconds.
                        Racoon is restarted cyclic and VPN is unuasable.

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