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

    DNS Resolver stops working after pppoe_restart_pppoe0

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 2 Posters 788 Views 2 Watching
    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.
    • M Offline
      MarcO42
      last edited by

      Hi,
      I had installed pfblockerng-devel and was pretty happy with the result.
      But after that I have only one issue left that I'm not knowing where it came from.
      Every night I do a manual reconnect with

      /var/etc/pppoe_restart_pppoe0

      After the reconnect is done my DSN Resolver (Unbound) stops working.

      I can only find this in my logs:

      Sep 27 08:11:08 router unbound[6507]: [6507:0] info: server stats for thread 0: 280 queries, 52 answers from cache, 228 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Sep 27 08:11:07 router unbound[6507]: [6507:0] info: service stopped (unbound 1.12.0).
Sep 27 08:11:07 router unbound[6507]: [6507:0] info: start of service (unbound 1.12.0).
Sep 27 08:11:07 router unbound[6507]: [6507:0] notice: init module 1: iterator

      Maybe someone can help me to find the bug/misconfiguration?
      Many thx
      MarcO

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

        @marco42

        Hi,

        Why would you have to reconnect manually ?
        I've used pppoe myself a couple of years ago, and pppoe was reconnecting itself - If recall well, the connection has a fixed duration, but a reconnect was done automatically.

        Just to be sure :

        11a80e4b-dce8-4559-8e80-f5c88c30120a-image.png

        Remove the check from DHCP registration (Unbound resolver settings).

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

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          MarcO42 @Gertjan
          last edited by

          @gertjan
          Hi Gertjan,
          I'd like to reconnect at that time because of my provider is normally reconnecting me after 24H.
          In the past his help me to prevent disconnects when we are gaming online.
          The DHCP Registration is currently checked. I have many clients in my network and I like use the custom names (DNS Names) to get access. When I now uncheck this box I'm losing this possibility, right?

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

            @marco42 said in DNS Resolver stops working after pppoe_restart_pppoe0:

            right?

            Right !
            What you also loose, is the fact that on every new lease, a,d every renewed lease, the resolver is restarted.

            For info, see the other 1000+ posts on this forum about this subject.

            Execute :

            grep 'start' /var/log/resolver.log

            and check if you're ok with the frequency.

            If not, uncheck "DHCP Registration", and make Static DHCP leases for all you known devices.
            You'll have best of both worlds.

            Btw : Why would 'gaming' disconnect a pppoe connection ?
            As far as I recall, pppoe - somewhat like the the classic DHCP-client-lease, renew when it expires.
            I always saw, on fixes times, my ISP closing the connection because of max duration.
            The pppoe part of pfSense always auto renews.

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

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              MarcO42 @Gertjan
              last edited by

              @gertjan said in DNS Resolver stops working after pppoe_restart_pppoe0:
              Oh, I think I missed a part. I have all my clients in the DHCP list to give them a "static" IP

              grep 'start' /var/log/resolver.log

              WTF?

              Sep 24 11:49:35 router unbound[78640]: [78640:0] info: start of service (unbound 1.12.0).
Sep 24 12:07:52 router unbound[78640]: [78640:0] notice: Restart of unbound 1.12.0.
Sep 24 12:08:40 router unbound[78640]: [78640:0] info: start of service (unbound 1.12.0).
Sep 24 12:08:40 router unbound[78640]: [78640:0] notice: Restart of unbound 1.12.0.
Sep 24 12:09:28 router unbound[78640]: [78640:0] info: start of service (unbound 1.12.0).
Sep 25 00:48:54 router unbound[77156]: [77156:0] info: start of service (unbound 1.12.0).
Sep 25 03:50:19 router unbound[77156]: [77156:0] notice: Restart of unbound 1.12.0.
Sep 25 03:51:18 router unbound[77156]: [77156:0] info: start of service (unbound 1.12.0).
Sep 25 03:52:22 router unbound[44665]: [44665:0] info: start of service (unbound 1.12.0).
Sep 25 03:53:27 router unbound[91449]: [91449:0] info: start of service (unbound 1.12.0).
Sep 25 07:58:21 router unbound[16478]: [16478:0] info: start of service (unbound 1.12.0).
Sep 25 07:58:21 router unbound[16478]: [16478:0] notice: Restart of unbound 1.12.0.
Sep 25 07:59:09 router unbound[16478]: [16478:0] info: start of service (unbound 1.12.0).
Sep 25 22:55:57 router unbound[16478]: [16478:0] notice: Restart of unbound 1.12.0.
Sep 25 22:56:49 router unbound[16478]: [16478:0] info: start of service (unbound 1.12.0).
Sep 25 22:56:49 router unbound[16478]: [16478:0] notice: Restart of unbound 1.12.0.
Sep 25 22:57:44 router unbound[16478]: [16478:0] info: start of service (unbound 1.12.0).
Sep 26 00:47:21 router unbound[31994]: [31994:0] info: start of service (unbound 1.12.0).
Sep 26 00:55:57 router unbound[31994]: [31994:0] notice: Restart of unbound 1.12.0.
Sep 26 00:56:47 router unbound[31994]: [31994:0] info: start of service (unbound 1.12.0).
Sep 26 00:56:47 router unbound[31994]: [31994:0] notice: Restart of unbound 1.12.0.
Sep 26 00:57:36 router unbound[31994]: [31994:0] info: start of service (unbound 1.12.0).
Sep 26 03:50:15 router unbound[31994]: [31994:0] notice: Restart of unbound 1.12.0.
Sep 26 03:51:12 router unbound[31994]: [31994:0] info: start of service (unbound 1.12.0).
Sep 26 03:52:16 router unbound[90266]: [90266:0] info: start of service (unbound 1.12.0).
Sep 26 03:53:20 router unbound[63772]: [63772:0] info: start of service (unbound 1.12.0).
Sep 26 07:39:21 router unbound[99898]: [99898:0] info: start of service (unbound 1.12.0).
Sep 26 07:39:21 router unbound[99898]: [99898:0] notice: Restart of unbound 1.12.0.
Sep 26 07:40:13 router unbound[99898]: [99898:0] info: start of service (unbound 1.12.0).
Sep 27 00:48:51 router unbound[35994]: [35994:0] info: start of service (unbound 1.12.0).
Sep 27 03:50:15 router unbound[35994]: [35994:0] notice: Restart of unbound 1.12.0.
Sep 27 03:51:14 router unbound[35994]: [35994:0] info: start of service (unbound 1.12.0).
Sep 27 03:52:18 router unbound[74797]: [74797:0] info: start of service (unbound 1.12.0).
Sep 27 03:53:24 router unbound[57862]: [57862:0] info: start of service (unbound 1.12.0).
Sep 27 03:55:01 router unbound[82297]: [82297:0] info: start of service (unbound 1.12.0).
Sep 27 03:55:01 router unbound[82297]: [82297:0] notice: Restart of unbound 1.12.0.
Sep 27 03:55:48 router unbound[82297]: [82297:0] info: start of service (unbound 1.12.0).
Sep 27 07:32:00 router unbound[82297]: [82297:0] notice: Restart of unbound 1.12.0.
Sep 27 07:33:03 router unbound[82297]: [82297:0] info: start of service (unbound 1.12.0).
Sep 27 07:34:14 router unbound[91514]: [91514:0] info: start of service (unbound 1.12.0).
Sep 27 07:35:25 router unbound[19671]: [19671:0] info: start of service (unbound 1.12.0).
Sep 27 07:37:03 router unbound[63760]: [63760:0] info: start of service (unbound 1.12.0).
Sep 27 07:37:03 router unbound[63760]: [63760:0] notice: Restart of unbound 1.12.0.
Sep 27 07:37:52 router unbound[63760]: [63760:0] info: start of service (unbound 1.12.0).
Sep 27 08:06:20 router unbound[63760]: [63760:0] notice: Restart of unbound 1.12.0.
Sep 27 08:07:20 router unbound[63760]: [63760:0] info: start of service (unbound 1.12.0).
Sep 27 08:08:26 router unbound[36958]: [36958:0] info: start of service (unbound 1.12.0).
Sep 27 08:09:36 router unbound[70799]: [70799:0] info: start of service (unbound 1.12.0).
Sep 27 08:11:07 router unbound[6507]: [6507:0] info: start of service (unbound 1.12.0).
Sep 27 08:11:08 router unbound[6507]: [6507:0] notice: Restart of unbound 1.12.0.
Sep 27 08:11:59 router unbound[6507]: [6507:0] info: start of service (unbound 1.12.0).
Sep 27 11:55:25 router unbound[90409]: [90409:0] info: start of service (unbound 1.12.0).

              Ok, this is really to much, many thank for the hind.

              @gertjan said in DNS Resolver stops working after pppoe_restart_pppoe0:

              @marco42 said in DNS Resolver stops working after pppoe_restart_pppoe0:
              Btw : Why would 'gaming' disconnect a pppoe connection ?...

              Other way around. My provider forced a disconnect when I'm longer online than 24H.
              This disconnect is kicking me out of games.

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

                @marco42 said in DNS Resolver stops working after pppoe_restart_pppoe0:

                Ok, this is really to much

                15 times a day ... seen worse.

                A restart will happens when the pppoe reconnects, as the WAN interface changes. That's normal.
                pfBlockerNG could also restart unbound.

                Btw : pppoe can time out, that's normal.
                If your not gaming 24/24h, you could manually restart the connection at, for example, 07h00 AM.
                From that moment on, the next reconnect will also happens the next day at the same time.
                Use an UPS, and you'll exclude power loss reboots, which will change that moment.

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

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  MarcO42 @Gertjan
                  last edited by

                  Hey @gertjan,
                  many thx for your help.
                  I just checked the restart frequency and got this result:

                  grep 'start' /var/log/resolver.log

                  Sep 28 03:53:30 router unbound[36453]: [36453:0] info: start of service (unbound 1.12.0).

                  Have a great day
                  MarcO

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

                    @marco42 said in DNS Resolver stops working after pppoe_restart_pppoe0:

                    I just checked the restart frequency and got this result:

                    Keep in mind that these log files could have been rotated, which means older records have been purged. In that case, you'll find less results.
                    Always have a look at the file, as log files are there to be looked at.

                    Mine was rotated last month, on august 13 :

                    Aug 13 14:36:00 pfsense newsyslog[90565]: logfile turned over due to size>1024K
                    <31>1 2021-08-13T14:36:03.090423+02:00 pfsense.athome.tld unbound 799 - - [799:0] debug: validator[module 1] operate: extstate:module_state_ini>
                    <
                    ........
                    <30>1 2021-09-28T02:35:18.370449+02:00 pfsense.athome.tld unbound 45024 - - [45024:0] info: generate keytag query _ta-4f66. NULL IN

                    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 1
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.