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

    Gateway shows as being down, but isn't.

    General pfSense Questions
    8
    11
    2.5k
    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.
    • R
      rizwan602
      last edited by

      Hi,

      Sometimes my pfSense box shows that a gateway is down, even though the RTT shows a healthy 32ms but the packet loss shows 100%. I know the gateway is up because if I connect my laptop to the back of the DSL modem that pfSense connects to, I get connectivity to the internet without any problems. Consquently, that gateway is taken out of the routing group.

      Please see attached image. Look at GATEWAYA – thats the one showing being down but with 32ms or so RTT.

      Rizwan
      ![pfsense gateway down.png](/public/imported_attachments/1/pfsense gateway down.png)
      ![pfsense gateway down.png_thumb](/public/imported_attachments/1/pfsense gateway down.png_thumb)

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

        turn off gateway ip monitoring on the WAN interface, see if that helps.

        1 Reply Last reply Reply Quote 0
        • R
          rizwan602
          last edited by

          I have turned off gateway monitoring and things start working again, but I need to keep the gateway monitoring on.

          I have found that if the gateway goes down and comes back up pfSense still thinks its down. The only way I can get it to work is change the Monitor IP address on the gateways screen, save / apply the setting, and then change it back, save / apply and it automagically starts working again, until the gateway is either down or rebooted later. I constantly have to massage this setting.

          I have tried many differnet Monitor IP addresses. I've tried 4.2.2.1, 8.8.8.8 and many others. Same behavior.

          Is this an issue others are experiencing too?

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

            I am having the exact same problem, right down to your workaround with changing the monitor ip and it showing online again.

            Were you ever able to find a better solution?

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

              Is the monitoring IP going down or blacklisting you temporarily due to high traffic?

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

                The monitor ip is set to 8.8.8.8 right now, so I doubt its blacklisting me, and it's not being blacklisted by anything on my end, as far as I can tell.

                The gateway status appears to be showing an accurate RTT, but it also shows offline and 100% loss. The gateway still works fine and my traffic is still sent over it, but it shows offline and 100% loss.

                Restarting the apinger service seems to fix it temporarily, but it ends up showing offline again at some point.

                It's not a big issue for me since it's not in a gateway group like the OP's, I'm just curious as to what's causing it more than anything.

                1 Reply Last reply Reply Quote 0
                • T
                  tokiebonilla
                  last edited by

                  @finack:

                  I am having the exact same problem, right down to your workaround with changing the monitor ip and it showing online again.

                  Were you ever able to find a better solution?

                  Same here, same exact problem with Gateway monitoring.

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by

                    apinger is broken.  It does all sorts of nonsense.  It's pretty unthinkable that they don't do a 2.1.6 to fix it.  Wait for 2.2 they say.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 0
                    • E
                      edosselio
                      last edited by

                      @Derelict:

                      apinger is broken.  It does all sorts of nonsense.  It's pretty unthinkable that they don't do a 2.1.6 to fix it.  Wait for 2.2 they say.

                      Hello,
                      any news about that? We're now on 2.2.4 but the problem still exists.
                      Apinger works perfectly when a gateway goes down and the traffic is correctly routed to the other one; but when the gateway comes up apinger does not do the "failback" until i don't manually restart the process….

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @edosselio:

                        any news about that? We're now on 2.2.4 but the problem still exists.

                        No, no news at all… apinger is still the same unfixable garbage code.

                        1 Reply Last reply Reply Quote 0
                        • E
                          edosselio
                          last edited by

                          Ok, for now i've set a workaround cron task running every 15 minutes:

                          /usr/bin/killall -9 apinger && /usr/local/sbin/apinger -c /var/etc/apinger.conf

                          Thanks,

                          Edoardo

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post