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

    Apinger "again"

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    20 Posts 5 Posters 17.1k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      You have a RTT of 1s? (1000ms)  :o

      Here I am seeing ~25ms on one wan and 6-7ms on the other.

      What did you change in apinger.conf?

      Steve

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

        Hi,

        There might be something I not fully understood.

        The log from wireshark shows the ping from apinger at each seconds, see attached file.
        Also look for record 5161, 5212 and 5243 they are the reason for me to have stopped ICMPs from leaving the box, mainly because I am not 100% what it means "5161","2011-06-13 18:29:29.539365","207.204.241.59","200.82.252.149","ICMP","174","Destination unreachable (Host administratively prohibited)". I got a bit surprised when I started to see "prohibited" messages.

        For apinger the only "hand" change I did were to try to change rrd interval to 60s, but that did not change the ping frequency - guess wrong place to do.
        I would think a minute or two will be fine and will limit the flood of pings, but how to change the frequency?

        Ideas?

        Steen

        [apinger.conf SH.txt](/public/imported_attachments/1/apinger.conf SH.txt)
        [Capture pfSense 13 June 2011 01 SH.txt](/public/imported_attachments/1/Capture pfSense 13 June 2011 01 SH.txt)

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

          Hello,

          Really really need to get help to change the apinger frequency - anyone please.  :'(  :-[

          Thanks Steen

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

            Why do you need to change the frequency? If you have the thresholds set appropriately for your connection you will only get anything in the logs when the latency/packet loss changes to something higher?

            Steve

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

              Hi Stephen,

              Not worried over my logs, but I do not feel comfortable by hammering out a ping every each second, my ISP is already making noise over this.
              Secondly my connection is not the more better, so often the connection is down or gives very poor response.
              For me a ping each one minute or two will be good, but I cannot find the place to change the ping frequency. Tried in the aping.conf, but whatever I did don't seams to have any effect.

              I tried to change here:
              target default {

              How often the probe should be sent

              interval 1s
              to, 60s, 120s, 180s but no change the ping frequency.

              The rest of aping.conf looks like this:

              How many replies should be used to compute average delay

              for controlling "delay" alarms

              avg_delay_samples 10

              How many probes should be used to compute average loss

              avg_loss_samples 50

              The delay (in samples) after which loss is computed

              without this delays larger than interval would be treated as loss

              avg_loss_delay_samples 20

              Names of the alarms that may be generated for the target

              alarms "down","delay","loss"

              Location of the RRD

              #rrd file "/var/db/rrd/apinger-%t.rrd"
              }
              alarm delay "WANdelay" {
              delay_low 400ms
              delay_high 1000ms
              }
              alarm down "WANdown" {
              time 30s
              }

              BR// Steen

              1 Reply Last reply Reply Quote 0
              • E
                eri--
                last edited by

                Heh when 1 ping every 1secs is too much?
                You push packets into that network at a much faster speed and the uplink is suppose to handle!

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

                  Yes, agree…
                  But my uplink is often <128Mbps, and it have high latency and disconnects often, modem reboots, etc., etc., I am trying to work with the ISP (who basically don't give a damn due to lack of competition in my area), and for this I do not want to ping him too often. Using VisualRoute I try to show him his latency in his network, and connection (Up/Down) that often are 50/60% less than what I subscribe/pay for.
                  So if and there is a possibility from what I have read I would like to change the ping frequency.

                  BR// Steen

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

                    I assume you mean 128Kbps?  ;)

                    Can you ping your cable modem instead?

                    Steve

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

                      oops  ::) :o :-[ forgot the 0.

                      Yes, I can, but the Cable Modem changes address whenever the modem reboots, so I would have to manually to look up and change.
                      Pinging the GW is great, but for a period I would like to send the pings less often that is all.

                      1 Reply Last reply Reply Quote 0
                      • V
                        Veni
                        last edited by

                        @seh2000:

                        […] but I do not feel comfortable by hammering out a ping every each second, my ISP is already making noise over this.

                        Check this post: http://forum.pfsense.org/index.php/topic,35531.msg183946/topicseen.html#msg183946

                        It works for me. Pinging over a 3G connection every second including every DNS request going to every backup WAN
                        generates some traffic over the 3G connection.

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

                          Hello Veni,

                          MANY THANKS!

                          Just what I been looking for!

                          Tried 60s first when confirmed to be sent each 60s then I changed to 5s!

                          BR// Steen

                          1 Reply Last reply Reply Quote 0
                          • V
                            Veni
                            last edited by

                            @seh2000:

                            […] I changed to 5s!

                            I forgot to mention that you need to reset this value every time after you do an update/upgrade of pfSense,
                            because that file will be overwritten with the one downloaded.

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

                              Hi Veni,

                              Thanks, I already found out the "hard way", but many thanks for coming back!

                              Take care - Steen

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