The most time the gateways show status unknown



  • I updated 6 pfsenses to
    2.1-RC1  (amd64)
    built on Thu Aug 15 03:12:29 EDT 2013
    FreeBSD 8.3-RELEASE-p9

    All 6 shows the most time unknown for gateway status.
    For a short time they will be green.
    The dashboard will be slow on loading.


  • Banned

    Mine were fluctuating between Unknown and Pending due to an IPv6 kaboom… Best to skip this snapshot, and probably a couple of coming ones...  :-\



  • 2.1-RC1  (amd64)
    built on Sat Aug 17 21:32:08 EDT 2013
    FreeBSD 8.3-RELEASE-p9

    apinger is now fully working again, but dashboard still shows unknown gateway status the most time.



  • using: Tue Aug 27 16:56:42 EDT 2013

    The most time the gateways on dashboard shows "~" for IP, RTT and Loss while the status is "unknown".



  • 2.1-RC1  (amd64)  built on Mon Sep 2 07:02:23 EDT 2013

    still having this problem.
    Am I the only one?



  • @ggzengel:

    2.1-RC1  (amd64)  built on Mon Sep 2 07:02:23 EDT 2013

    still having this problem.
    Am I the only one?

    I'm running

    2.1-RC1 (i386)
    built on Thu Aug 29 16:33:12 EDT 2013
    FreeBSD 8.3-RELEASE-p10

    and Status -> Gateways shows online and "sensible" values. Gateways status on the dashboard shows similar values.



  • Strange. I have this on 6+ pfsenses, each with different configs and histories.
    If I look at status>Gateways they are the most time on pending. This changed with update a couple of weeks ago.



  • Its working fine for me on several 2.1 firewalls I have. The only problem I have is on a couple of them apinger is sending out the pings from the interface that holds the default gateway instead of the interface whose gateway I am trying to monitor. Workaround I have in place is to add a static route for the monitor IP and point it to the gateway I am trying to monitor.

    Do some packet captures and see if pings are getting sent to the monitor IP from the correct interface and are being responded to.

    If there are no pings going out then check is the apinger process is running.

    If the pings are going out then check the contents of cd /var/run/apinger.status

    Are your RRD quality graphs not getting updated either?


Log in to reply