I got this warning in my Pi-hole after enabling the DHCP server:
duplicate IP address 2804:d55:5200:6600:5522:a2bc:8ded:8fd1 (scarlett) in dhcp-config directive
This is kinda embarrassing, but the Pi-hole is working fine, but I have no idea where to find this dhcp-config directive to remove the duplicated IP. I've looked (and grep) in every file on /etc/dnsmasq.d and /etc/pihole and found no trace of that IPv6 address and the dhcp-config text.
May someone tell me where to look better?
Your debug log has scarlett appearing in quite a few locations, including local hostnames and CNAMEs.
You are also trying to use scarlett as a name for the machine that is hosting your Pi-hole as well as for a DHCP client of your Pi-hole's DHCP server.
Try removing that static DHCP lease client, or change its name.
Likely unrelated, but I notice that you'ce added an actual IP address to your loopback interface:
*** [ DIAGNOSING ]: Network interfaces and addresses
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet 192.168.99.1/24 brd 192.168.99.255 scope global lo:0
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
What's the purpose of that?
Thank you, yes, the warning was for the lease for the server itself. I copy the static leases from the router and fogot to take that line out.
About the IP in the loopback interface, that is for dnscryptproxy bind to the port 53 without messing with the Pi-hole. For some reason I can't remember, leaving it bound just to port 5300 didn't work and of course couldn't use the same port on the same ip as the Pi-hole. That extra IP in the loopback made dnscryptproxy happy and all worked.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.