[[SUPPORT] pihole for unRaid - Spants repo]

6 minutes ago, Tibbe said:

I managed to get it working using a custom Docker network (called "proxy"). My machine is at 192.168.5.100:

 

Care to share your networking settings in unraid too? 

[[SUPPORT] pihole for unRaid - Spants repo]

I think the difference between your setup and mine is on the br0.7 config. I only have my default br0. No VLANs enabled. Attempting to give my instance of pihole a different IP worked to access the interface, but I think I probably need to configure it via VLANs for it to work.

 

In the meantime, I just put pihole on an old model B. Would rather have it in unraid.

 

What's your config for networking? 

 

 

[[SUPPORT] pihole for unRaid - Spants repo]

35 minutes ago, PeteAsking said:

Must be your setup because I just reinstalled as a test and the template works perfectly and updates lists etc no issue.

Can you share your docker config screen/settings? 

 

I thought it was related to the Settings > Docker > Advanced view > Host access to custom networks. Mine was initially disabled.

 

Stopped Docker > Changed to enabled > Started docker > Force updated the pihole docker. It still doesn't see the internet or that it has an IPv4 address assigned to it according to my diag.

 

I think the key section of my debug diag log is this:

Quote

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the br0 interface.

[✗] No IPv6 address(es) found on the br0 interface.

 

Pihole docker settings

Quote

Network Type: Custom : br0

Fixed IP address (optional): 192.168.1.2              Subnet: 192.168.1.0/24

...

ServerIP: 192.168.1.2

...

INTERFACE: br0

 

 

[[SUPPORT] pihole for unRaid - Spants repo]

Adding to this discussion.

 

I did a fresh install of pihole and am unable to update gravity. The config alerts if I attempt to use 127.0.0.1 as DNS1. 

 

My list of hosts blocked is reported as '-2'.

 

Attempts to update gravity take a very long time but ultimately fail with the same errors of 

[✗] DNS resolution is currently unavailable

[✗] DNS resolution is not available

 

Attempted to reload the docker with DNSMASQ_USER set to 'root' but still have the same errors. Am able to access the web interface buy my custom password is not being used for accessing the web gui. It still uses the default 'admin'.

 

Confirmed a reinstall has the same problem even after I wipe out the /appdata/pihole dir to start fresh.

 

Can't upload debug log. These errors show in the debug and seem significant:

 

=========

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the br0 interface.

[✗] No IPv6 address(es) found on the br0 interface.

*** [ DIAGNOSING ]: Ports in use

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve  on lo (127.0.0.1)
[✓] No IPv4 address available on eth0@if34
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] No IPv6 address available on lo
[✓] No IPv6 address available on eth0@if34
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   DHCP packets received on interface tunl0: 0
   DHCP packets received on interface eth0: 0
   DHCP packets received on interface ip_vti0: 0

=========

Interface should be br0 but this shows no IP address available