Navigation

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

    Problem with gateway's monitoring

    General pfSense Questions
    3
    4
    972
    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.
    • B
      baba last edited by

      Hello, i see several of this in System Logs:

      Oct 23 15:35:30 check_reload_status: Reloading filter
      Oct 23 15:35:30 check_reload_status: Reloading filter
      Oct 23 15:35:20 apinger: alarm canceled: IFEGW(xxx.xxx.xxx.xxx) *** down ***
      Oct 23 15:35:20 apinger: alarm canceled: DFGW(xxx.xxx.xxx.xxx) *** down ***
      Oct 23 15:35:20 apinger: ALARM: IFEGW(xxx.xxx.xxx.xxx) *** down ***
      Oct 23 15:35:20 apinger: ALARM: DFGW(xxx.xxx.xxx.xxx) *** down ***

      The two nics are on different physical network and different switch. I have also another two interface withoust this problem.
      I have also installed OpenNMS and it send me several email where detect the HTTP interface of pfsense is not responding.
      I supposed problem with my nics, but in the log i can't see an entry that say the NIC is down…
      In what log's file i can check if pfsense set interfaces to down?
      Thanks

      1 Reply Last reply Reply Quote 0
      • D
        deltalord last edited by

        I'm experiencing the same logfile pattern

        Mar 10 05:17:24	check_reload_status: Reloading filter
        Mar 10 05:17:25	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
        Mar 10 05:17:31	apinger: ALARM: NLVPN(IPADDRESS) *** NLVPNdown ***
        Mar 10 05:17:33	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
        Mar 10 05:17:34	apinger: alarm canceled: NLVPN(IPADDRESS) *** delay ***
        Mar 10 05:17:35	check_reload_status: Reloading filter
        Mar 10 05:17:41	apinger: ALARM: NLVPN(IPADDRESS) *** NLVPNdown ***
        Mar 10 05:17:43	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
        

        and so forth, but with a nice "feature" coming with it: 100% CPU Load. I see that the above mentioned Gateway shows high pings (4.000 ms up to 20.000 ms). I'm on 2.0.2-RELEASE  (i386) built on Fri Dec 7 16:30:14 EST 2012.

        1 Reply Last reply Reply Quote 0
        • H
          heper last edited by

          would you happen to have the same monitor ip on both wan connections ?

          1 Reply Last reply Reply Quote 0
          • D
            deltalord last edited by

            Edit: Oh, I'm sorry, you mean Monitor IP. No, all different on all interfaces (2 WAN, 2 VPN). But both VPNs have the same gateway IP.

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

            Products

            • Platform Overview
            • TNSR
            • pfSense
            • Appliances

            Services

            • Training
            • Professional Services

            Support

            • Subscription Plans
            • Contact Support
            • Product Lifecycle
            • Documentation

            News

            • Media Coverage
            • Press
            • Events

            Resources

            • Blog
            • FAQ
            • Find a Partner
            • Resource Library
            • Security Information

            Company

            • About Us
            • Careers
            • Partners
            • Contact Us
            • Legal
            Our Mission

            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

            Subscribe to our Newsletter

            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

            © 2021 Rubicon Communications, LLC | Privacy Policy