Still having issues with dual interfaces

Help
1

This time without Zentyal, set IP addresses manually, and set what I consider the appropriate settings with Webmin (will screenshot if requested)

Windows 10 says the IP configuration is invalid.

I think it's getting the IPv6 address from either the router, or from the 192 interface. I care so little about IPv6, so if I can get help to generate one for the interface I wish it to serve DHCP from, that would be a great help.

I know I need to run some commands, but what, I do not know. I think I have reinstalled at least 8 times now, trying to get this to work.

I was using Zentyal before as a step to assign IP addresses, but this was getting in the way of DNS and DHCP, although disabled

Debug Token:

ifg17ntk0i

2

Is this a Pi-hole issue? I don't see any mention of Pi-hole in your post.

2 Likes
5

There are several problems shown in your debug log, likely related to your network setup. You have the Pi-Hole and network on three different IP ranges (169.254.17.x, 192.168.0.x, 172.16.0.x).

The Pi-Hole is properly resolving domains from within it's loopback address, so that function works. The problem lies with the Pi-Hole communicating to your network.

Have you had Pi-Hole working properly prior to attempting a dual interface setup? If not, I recommend you do so. Then, once your Pi-Hole is working properly, expand it to dual NIC.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enx0014d1daa277 interface:
   169.254.17.7/16 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

[i] Default IPv4 gateway: 192.168.0.1
   * Pinging 192.168.0.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

[i] Default IPv6 gateway: fe80::9221:6ff:fe95:f0a4
   * Pinging fe80::9221:6ff:fe95:f0a4...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] ad.doubleclick.net.57933.9418.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve ad.doubleclick.net.57933.9418.302br.net via Pi-hole (172.16.0.1)
[✓] doubleclick.com is 216.58.212.110 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
[✓] agenciaclose.com is :: via localhost (::1)
[✗] Failed to resolve agenciaclose.com via Pi-hole (fd6e:edf8:1b69:0:203:dff:fe9b:bc59)
[✓] doubleclick.com is 2a00:1450:4009:80c::200e via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=enx0014d1daa277
    IPV4_ADDRESS=172.16.0.1/24
    IPV6_ADDRESS=fd6e:edf8:1b69:0:203:dff:fe9b:bc59
    ....
   DHCP_ACTIVE=true
   DHCP_START=172.16.0.3
   DHCP_END=172.16.0.254
   DHCP_ROUTER=172.16.0.1

-rw-r--r-- 1 root root 120 Sep 19 20:32 /etc/pihole/local.list
   192.168.0.2 mark
   fd6e:edf8:1b69:0:203:dff:fe9b:bc59 mark
   192.168.0.2 pi.hole
   fd6e:edf8:1b69:0:203:dff:fe9b:bc59 pi.hole
6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.