Closed iAmSaugata closed 2 years ago
Please, generate a debug token and paste only the token URL, found a few lines before the end of the log.
My debug token is : https://tricorder.pi-hole.net/glKsvdM3/
Now I am having 830+ logs in just 10 hours. https://imgur.com/a/NAUiICT
And currently 27 clients are getting IP from this DHCP server. https://imgur.com/a/5FGurpq
This is the Dockerfile for DHCP helper, which I am using.
FROM alpine:latest RUN apk --no-cache add dhcp-helper EXPOSE 67 67/udp ENTRYPOINT ["dhcp-helper", "-n"]
Anyone have any suggestion on this?
The problem is that your DHCP server is listening on the network interface, whose IP is from different range than defined in env variables (DHCP_START, DHCP_END), and it can't assign any valid address for containers in backend network. I do not know how to solve this, because of my lack of knowledge in networking. However, I tried to make a workaround. I tested it only with two containers in backend network: dhcp-helper and pihole, and it works fine.
I managed to get rid of these log message by adding another dhcp-range parameter do dnsmasq config.
In dnsmasq.d I created new file 99-tmp.conf with additional IP range for DHCP: dhcp-range=172.33.0.10,172.33.0.20,24h
.
This range should match the range of your pihole's IP. After a fresh start, no dnsmasq_warnings appear in log section.
In settings->dhcp you should see one additional record, with IP from range 172.33.0.x, assigned to your machine's hostname.
Maybe shared-network feature of dnsmasq is the way to go. I tried it with different combinations, but to no avail.
Hi, Thanks for your response, I will try it by adding one more range as you suggested. I still don't understand, why it is started all on a sudden, it was working without any such working for months, only throwing error since last 15+ days.
Update : After applying this, no more messages logged, and yes, there is one assignment for 172.33.0.18 | RaspberryPi
Regards, Saugata D.
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.
This is a: Bug
Details
Hi Everyone,
I am running PiHole with DHCP using DHCP Helper. I am also using PiHole as primary DNS for WireGuard VPN. I am using following Docker-Compose to deploying this, and this setup was working perfectly fine for last 3/4 months. Day before yesterday, while working with RPI hardware watchdog settings, I set it into a boot loop because of wrong configuration. Thankfully I am able to restore RPI using previous image backup. Most of the applications started working just after booting, but for some reason, one SQL db and pihole-FTL.db got corrupted, and I had to reconfigure it. This time I use Portainer Stack to deploy the setup using this Docker-Compose file, and all the container booted successfully, there was little issue with permission, which I had to fix manually.
Now the entire setup is working as expected, and I am am able to get IP address for my clients, but all on a sudden PiHole gets flooded with following warning messages. These messages referring to eth0, which is having container IP (172.33.0.100), and dhcp-helper forwarding DHCP request to this IP, hence if I use no-dhcp-interface=eth0, it will disable the IP allocation for clients.
no address range available for DHCP request via eth0
Any solution for this?
Related Issues
How to reproduce the issue
Environment data
docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
These common fixes didn't work for my issue
docker run
example(s) in the readme (removing any customizations I added)If the above debugging / fixes revealed any new information note it here. Add any other debugging steps you've taken or theories on root cause that may help.