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

    Dpinger issue

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 4 Posters 726 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.
    • C
      cheleby
      last edited by

      Hi all. I got dpinger service problem,everyday dpinger stopped and I reboot pfsense to connect again wan. I use pppoe connection. I see logs sendto error: 65. What is the problem ?

      Ekran görüntüsü 2025-01-17 102112.png

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @cheleby
        last edited by

        @cheleby

        Log please.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        C 1 Reply Last reply Reply Quote 0
        • C
          cheleby @Gertjan
          last edited by

          @Gertjan

          Jan 15 21:37:08	dpinger	87489	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 10.64.128.1 bind_addr 10.64.159.29 identifier "WAN_PPPOE "
          Jan 16 02:40:47	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:47	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:48	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:48	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:49	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:49	dpinger	87489	WAN_PPPOE 10.64.128.1: sendto error: 65
          Jan 16 02:40:50	dpinger	87489	exiting on signal 15
          
          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @cheleby
            last edited by

            @cheleby said in Dpinger issue:

            Jan 16 02:40:47 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:47 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:48 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:48 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:49 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:49 dpinger 87489 WAN_PPPOE 10.64.128.1: sendto error: 65
            Jan 16 02:40:50 dpinger 87489 exiting on signal 15

            That's your answer.
            The interface WAN (pppoe) lost connection / was taken down /failed.
            The dpinger instance running started at

            Jan 15 21:37:08 dpinger 87489 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr 10.64.128.1 bind_addr 10.64.159.29 identifier "WAN_PPPOE "

            bailed out. And that's ok, as there is no "WAN_PPPOE " anymore.

            Yo can experiment with :

            3384d78e-8a8f-4507-b3ab-31e65a2b1768-image.png

            so dpinger won't bother you anymore.

            Did the WAN_PPPOE reconstruct itself ?

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            C 1 Reply Last reply Reply Quote 0
            • C
              cheleby @Gertjan
              last edited by

              @Gertjan
              Yes, I reconstruct PPPOE mysef.
              I disabled gateway monitöring,I hope won't connection lost.

              GertjanG 1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan @cheleby
                last edited by

                @cheleby said in Dpinger issue:

                I hope won't connection lost.

                pppoe is always, like a DHCP lease, a connection with and know 'end'.
                That's why dpinger exists, it detects' that the link is lost, so it resets the connection, and this restart the establishment of a new pppoe connection.

                From what I recall, a pppe connection can be stopped with a command from the ISP side. The pooe software on the pfSense will 'ack' the stop, and restart the poe link by itself. This can generate a new WAN IP, so processes have to be restarted to reflect this change.

                If the pppoe goes down because the link quality is bad, then dpinger is even more important.
                Your ISP is just waiting ... but no traffic comes from you ...
                pfSense (pppoe) is waiting, no traffic comes from your ISP ....
                And you can wait forever.
                That's where dpinger comes in : no more ping replies over xx seconds : it resets then (rebuilds) connection.
                So again : If dpingger starts to loose to much ICMP packets, it can take action = reset the interface.

                And when you saturate the connection, so no more ICMP packets can go up and down, this will also have the same consequence : connection reset as dpinger can't ping (and receive) icmp packets anymore (while the connection was working just fine , but the pipe was full). Be ware : icmp packets have a lower priority ^^

                Back in the good old days when pppoe was a thing (here in France) I didn't know any better.
                These days, I'm actually glad that pppoe is gone.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

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

                  The better question there is why didn't dpinger restart when the PPPoE reconnected? Are there any errors shown?

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    cheleby @stephenw10
                    last edited by

                    @stephenw10 no error shown. When I try to start manually dpinger not starting. I have to reboot pfsense

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

                      Hmm, you might try running it manually at the CLI and see what error is shown there. If any.

                      1 Reply Last reply Reply Quote 0
                      • dennypageD
                        dennypage
                        last edited by

                        @cheleby Were you able to start dpinger via the command line to check the error as @stephenw10 suggested?

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