No Internet connection after pihole restart

Help Community Help
,
30

It all depends if other software, like for example PiVPN, have dropped an interface= line in their config files in the /etc/dnsmasq.d/ folder:

The only interfaces in my case that are of interest are eth0 and wg0 (Wireguard). Apparently Wireguard did not place any lines within the /etc/dnsmasq.d/ foler, thats why I created a file /etc/dnsmasq.d/99-interfaces.conf containing the line interface=wg0 and left the switch on Listen only on interface eth0. That worked.
But DanSchaper mentioned:

That will lock you up quite well. If there are more than one interface lines in the /etc/dnsmasq.d/ directory then you're going to inflict some damage on yourself. The Listen only options only read our config file (01-pihole) and has no idea what you set on other configuration files.

I removed that file again, base on DanSchapers comment. I think I was reading about that method some place else and it was recommended. If I understand you correctly, it could work that way?

I used denyinterfaces dummy0 sit0@NONE ip6tnl0@NONE wlan0 in the /etc/dhcpcd.conf file without wg0 since I need it for wireguard.

ip -br address show
lo               UNKNOWN        127.0.0.1/8 ::1/128
dummy0           UNKNOWN        fe80::a882:3f47:2eb0:18b5/64
sit0@NONE        DOWN
ip6tnl0@NONE     DOWN
eth0             UP             192.168.184.32/24 fd00::f727:e8bf:ffeb:d76f/64 2a02:945:2116:77e3:98a:82e5:8d4f:a687/64 fe80::8a2e:80e6:8d4c:2248/64
wlan0            DOWN
wg0              UNKNOWN        100.10.0.1/24 fd21:21:21::1/64

sudo journalctl -u dhcpcd
-- Logs begin at Tue 2020-11-03 16:55:37 CET, end at Tue 2020-11-03 16:57:00 CET. --
Nov 03 16:55:39 tinkerboard systemd[1]: Starting DHCP Client Daemon...
Nov 03 16:55:39 tinkerboard dhcpcd[1349]: no interfaces have a carrier
Nov 03 16:55:39 tinkerboard dhcpcd[1349]: no interfaces have a carrier
Nov 03 16:55:39 tinkerboard dhcpcd[1349]: forked to background, child pid 1499
Nov 03 16:55:39 tinkerboard dhcpcd[1349]: forked to background, child pid 1499
Nov 03 16:55:39 tinkerboard dhcpcd[1499]: dummy0: waiting for carrier
Nov 03 16:55:39 tinkerboard systemd[1]: Started DHCP Client Daemon.
Nov 03 16:55:39 tinkerboard dhcpcd[1499]: eth0: waiting for carrier
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: wlan0: waiting for carrier
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: dummy0: carrier acquired
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: DUID 00:01:00:01:87:36:2b:dd:8e:db:ca:14:8f:88
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: dummy0: IAID 22:45:87:36
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: dummy0: adding address fe80::d460:ec62:4ae9:5d7e
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: carrier acquired
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: IAID f6:f5:a7:3d
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: adding address fe80::8a1e:78f6:8f6a:1858
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: probing address 192.168.184.32/24
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: carrier lost
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: eth0: deleting address fe80::8a1e:78f6:8f6a:1858
Nov 03 16:55:41 tinkerboard dhcpcd[1499]: dummy0: soliciting an IPv6 router
Nov 03 16:55:42 tinkerboard dhcpcd[1499]: dummy0: soliciting a DHCP lease
Nov 03 16:55:43 tinkerboard dhcpcd[1499]: eth0: carrier acquired
Nov 03 16:55:43 tinkerboard dhcpcd[1499]: eth0: IAID f6:f5:a7:3d
Nov 03 16:55:43 tinkerboard dhcpcd[1499]: eth0: adding address fe80::8a1e:78f6:8f6a:1858
Nov 03 16:55:43 tinkerboard dhcpcd[1499]: eth0: probing address 192.168.184.32/24
Nov 03 16:55:44 tinkerboard dhcpcd[1499]: eth0: soliciting an IPv6 router
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: Router Advertisement from fe80::464e:4dee:fe73:ae65
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: adding address 2a02:908:2116:75f0:78a:82e5:8d4a:c357/64
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: adding address fd00::f727:e8bf:eefb:d51f/64
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: adding route to 2a02:908:2116:75f0::/64
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: adding route to fd00::/64
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: adding default route via fe80::464e:4dee:fe73:ae65
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: soliciting a DHCPv6 lease
Nov 03 16:55:45 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:55:46 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:55:48 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:55:49 tinkerboard dhcpcd[1499]: eth0: using static address 192.168.184.32/24
Nov 03 16:55:49 tinkerboard dhcpcd[1499]: eth0: adding route to 192.168.184.0/24
Nov 03 16:55:49 tinkerboard dhcpcd[1499]: eth0: adding default route via 192.168.184.1
Nov 03 16:55:52 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:55:53 tinkerboard dhcpcd[1499]: dummy0: no IPv6 Routers available
Nov 03 16:56:00 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:56:16 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode
Nov 03 16:56:49 tinkerboard dhcpcd[1499]: eth0: DHCPv6 REPLY: in stateless mode

Since I disabled the network manager, all clients that are listed in pihole have just an IPv4 and no IPv6 address anymore. Is that OK does this affect the functionality anyhow?

34

Thats the proper way.

Good one!

Very very little.
Just make sure that any IPv6 related router settings on the LAN side are disabled that could cause a DNS leak through the IPv6 router advertised DNS server(s).
You dont need IPv6, it complicates things and you have to do everything twice for IPv4 as well as IPv6.

35

Until another choice is made like "Listen All Interfaces". Then Pi-hole will remove the interface line from the file it knows about (01-pihole.conf) and assume that no other files have configured that setting. 99-interfaces will still contain interface=wg0 and thus lock Pi-hole to that interface, even though "Listen All" is what was clicked and what we will see in trying to provide user assistance.

1 Like
36

Yep, thats what I found out by trial error not reading the man page first :smiley:

37

Very very little.
Just make sure that any IPv6 related router settings on the LAN side are disabled that could cause a DNS leak through the IPv6 router advertised DNS server(s).
You dont need IPv6, it complicates things and you have to do everything twice for IPv4 as well as IPv6.

Understood. Will have a look with regards to the router IPv6 settings.
I agree, IPv6 seems to be still all Greek to me.

Until another choice is made like "Listen All Interfaces". Then Pi-hole will remove the interface line from the file it knows about (01-pihole.conf) and assume that no other files have configured that setting. 99-interfaces will still contain interface=wg0 and thus lock Pi-hole to that interface, even though "Listen All" is what was clicked and what we will see in trying to provide user assistance.

Good explanation. That even I understand.
I don't wanna stress it. Just a last question in this regard, because somehow my pihole does ignore the wg0 interface as soon the switch is on Listen on all interfaces. At least directly after a restart. During a new installation all interfaces are properly detected by pihole even wg0. Unfortunately during the installation I just allowed to choose one interfaces and can not choose those interfaces that are really necessary (eth0 and wg0) for my setup.
What if I go back using the 99-interface.conf and add not just interface=wg0 to that file I also add interface=eth0 to it and switch to Listen on all interfaces and leave it there??? Would that break the functionality down the road as well some time???

Thanks guys for that great support.

38

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