Navigation

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

    Probe Interval

    General pfSense Questions
    4
    6
    1424
    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
      G.D. Wusser Esq. last edited by

      Please explain what does the following mean.
      “How often that an ICMP probe will be sent in seconds. Default is 1.”

      How many seconds before the next probe is sent?
      Or
      How many probes will be sent in a second?

      If I want one probe sent every ten seconds, should I put 10 or 0.1 in the box?
      Thank you.

      1 Reply Last reply Reply Quote 0
      • N
        NOYB last edited by

        “How often that an ICMP probe will be sent in seconds. Default is 1.”
        Please note the plurality of the word "seconds".

        Perhaps some punctuation in this description would be helpful.
        “How often that an ICMP probe will be sent, in seconds. Default is 1.”

        1 Reply Last reply Reply Quote 0
        • G
          G.D. Wusser Esq. last edited by

          @NOYB:

          “How often that an ICMP probe will be sent in seconds. Default is 1.”
          Please note the plurality of the word "seconds".

          Perhaps some punctuation in this description would be helpful.
          “How often that an ICMP probe will be sent, in seconds. Default is 1.”

          “How often” implies frequency. But “interval” impels otherwise. I am confused.
          What number do I need to put there in my case?

          1 Reply Last reply Reply Quote 0
          • BBcan177
            BBcan177 Moderator last edited by

            Here is a post about setting this too low and causing a lot more load over the course of a month.

            https://forum.pfsense.org/index.php?topic=56224.0

            1 Reply Last reply Reply Quote 0
            • B
              biggsy last edited by

              There was a discussion about the name of the setting.  I guess "interval" won out in the end.

              Perhaps the description was not adjusted accordingly.  Should probably be "The time, in seconds, between ICMP probes of the monitored gateway or alternative IP".

              EDIT: added "or alternative IP".  This was the discussion

              1 Reply Last reply Reply Quote 0
              • N
                NOYB last edited by

                It is consistent with other descriptions.  e.g. "Low and high thresholds for latency in milliseconds. Default is 200/500."

                Also please be sure to read the explanation and example at the bottom of the advanced section.

                Given those, it should become clear that it is a time, in seconds, that is being entered.

                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