Pihole not listening on wireguard interface despite "Listen on all interfaces" is set

DL6ER · April 6, 2020, 5:13pm

None of these two trigger any sort of update. Both are really just passive activities.

Opening the web UI might involve resolving pi.hole, but that's it. pihole status involves sending an empty package (not even a valid DNS packet!) to port 53. That shouldn't do anything either:

github.com

pi-hole/pi-hole/blob/2de5362adc2c1c780eac1ab39e466875143091d5/pihole#L255


      
              echo -e "  ${COL_LIGHT_RED}Invalid option${COL_NC}
            Try 'pihole logging --help' for more information."
              exit 1
            fi
            restartDNS
            echo -e "${OVER}  ${TICK} ${str}"
          }
          
          statusFunc() {
            # Determine if service is running on port 53 (Cr: https://superuser.com/a/806331)
            if (echo > /dev/tcp/127.0.0.1/53) >/dev/null 2>&1; then
              if [[ "${1}" != "web" ]]; then
                echo -e "  ${TICK} DNS service is running"
              fi
            else
              case "${1}" in
                "web") echo "-1";;
                *) echo -e "  ${CROSS} DNS service is NOT running";;
              esac
              return 0
            fi

Re-reading your statement,

you might have meant that FTL does not magically acquire new interfaces but only after a query has been made (from an already accepted interface!) before any queries from a new interface are accepted. This might be the case and may be a bug in dnsmasq. Users participating in the beta testing could check of FTL's branch update/dnsmasq to get the bleeding-edge dnsmasq code. This may or not resolve issues.