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

    Kill states and gateway down logging

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 3 Posters 1.0k 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.
    • I Offline
      IB
      last edited by

      Hello

      We use pfSense 2.3.2 with two internet link. It is not clear installation, but upgrade from 2.2.6->2.3.1. I have questions:

      1. When I check "State Killing on Gateway Failure" on System->Advanced->Miscellaneous, and gateway go down - which states entries cleared? All? Or  entries for failed gateway only?
      2. In previous versions, when gateway go down, it was a messages like "May  4 06:53:09 pfSense apinger: ALARM: GWLAN(192.168.50.1)  *** down ***" in gateway log. Now I not see this messages. Is it by design, or upgrade result?
      3. How I can check gateway state externally? In Zabbix agent or SNMP monitor I can check interfaces only, no gateway. Write own script (with ping, dpinger, etc) only? Or method for check pfsense gateway state exists? By log monitoring (see #2), or some command execution?

      1 Reply Last reply Reply Quote 0
      • G Offline
        GilbyDettori
        last edited by

        +1

        I'm trying to figure this out also, without having to use SSH and wrapping some dpinger commands.
        I'm surprised there's no apparent OID for gateway state?

        thanks!
        D.

        1 Reply Last reply Reply Quote 0
        • W Offline
          wbond
          last edited by

          @IB:

          3. How I can check gateway state externally? In Zabbix agent or SNMP monitor I can check interfaces only, no gateway. Write own script (with ping, dpinger, etc) only? Or method for check pfsense gateway state exists? By log monitoring (see #2), or some command execution?

          In Zabbix you could try adding a trigger for something like {pfsense:net.if.out[igb1].last()}=0 using the Template OS FreeBSD > Network Interfaces to tell if there's been no outbound traffic on an interface for a period of time.  I think you need the Zabbix agent package installed for this to work, but not positive.

          I have something like this monitoring both WAN interfaces and it seems to do the trick.

          Bill

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