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

    Warning messages

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 3 Posters 2.3k 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.
    • S
      sirdir
      last edited by

      Hi!

      I have a somewhat flakey internet line and I'd like to know wether there's a possibility to limit the rate of warning messages.
      I sometimes get a dozen warning messages per minute or even more… (MONITOR: GW_WAN is down, removing from routing group PrioTelitec

      MONITOR: GW_WAN is down, removing from routing group PrioTelefonica
      MONITOR: GW_WAN is down, removing from routing group PrioTelefonica
      MONITOR: GW_WAN is down, removing from routing group PrioTelitec
      MONITOR: GW_WAN is down, removing from routing group PrioTelitec
      MONITOR: GW_WAN is down, removing from routing group LoadBalance
      MONITOR: GW_WAN is down, removing from routing group PrioSat
      MONITOR: GW_WAN is down, removing from routing group LoadBalance
      MONITOR: GW_WAN is down, removing from routing group PrioSat
      MONITOR: GW_WAN has high latency, removing from routing group LoadBalance

      and so on and so on...
      Is there a way to limit this to one message per interface every x minutes?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        There is.  :)
        You can tune apinger, the process that monitors your WAN connections, to use values more suitable to your connection.
        Go to System: Routing: in the GUI. In the gateways tab edit your gateways, click the advanced button and enter some suitable values for latency or packet loss.

        I believe the default latency values are 200 and 500ms. If your normal ping times are around that you will be seeing constant alarms.

        The wording on this page needs to be changed, it's confusing. I've read it many times, I've read many descriptions, I've read the source code to try and understand it. "These define the low and high water marks for latency in milliseconds" would seem to imply that a latency below the "low water mark" will trigger a warning but that's patently not true.  :P

        I believe the actual operation is to issue a warning if the latency goes above the first number and to mark it down directly if it goes above the second number. Someone please correct me if I'm wrong on this, it's a whole since I looked into it.

        Steve

        1 Reply Last reply Reply Quote 0
        • S
          sirdir
          last edited by

          Hi!

          OK, but that doesn't really solve my problem. There really IS a problem in the moment when I get the warning message, I just don't see the point in getting 50 warning messages per minute.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, well you can change the frequency with which apinger checks the gateway status. If you changed it from 1 second to 60 second intervals you could only ever have a maximum of 1 warning a minute. Of course it may slow down the reconnect time as well.
            The adjustment is on the same tab in gateways.

            Steve

            1 Reply Last reply Reply Quote 0
            • S
              sirdir
              last edited by

              @stephenw10:

              Hmm, well you can change the frequency with which apinger checks the gateway status. If you changed it from 1 second to 60 second intervals you could only ever have a maximum of 1 warning a minute. Of course it may slow down the reconnect time as well.
              The adjustment is on the same tab in gateways.

              Steve

              OK, I know that. So maybe one could see that as a suggestion: I get up to 60 warning messages a minute. This should be configurable ('fire an alarm every … seconds only')...
              But to be honest, I think something has to be wrong in the algorithm of pfsense. I have set it now to fire an alarm after 60 probes, so how can I get an alarm every second?
              And by the way, I have my lines in several routing groups and of course I get a mail for every routing group the line is removed from...
              It's quite annoying.
              Other suggestion: have the option to disable those warning messages altogether...

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @sirdir:

                But to be honest, I think something has to be wrong in the algorithm of pfsense. I have set it now to fire an alarm after 60 probes, so how can I get an alarm every second?
                [/quoteI
                It might be necessary to restart apinger to get it to notice the change in configuration.

                1 Reply Last reply Reply Quote 0
                • S
                  sirdir
                  last edited by

                  @wallabybob:

                  @sirdir:

                  But to be honest, I think something has to be wrong in the algorithm of pfsense. I have set it now to fire an alarm after 60 probes, so how can I get an alarm every second?

                  It might be necessary to restart apinger to get it to notice the change in configuration.

                  Anyway, I still think something is wrong. My wireless link is completely dead now, so how can I get 20 messages a minute stating the link is removed from a routing group if it is down and stays down?

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