Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DCHP No longer responding to Client Request after Pi-Hole Update to v5.18.3 #5702

Closed
angeloluidens opened this issue Jul 8, 2024 · 3 comments
Labels

Comments

@angeloluidens
Copy link

angeloluidens commented Jul 8, 2024

Versions

Pi-hole version is v5.18.3 (Latest: v5.18.3)
web version is v5.21 (Latest: v5.21)
FTL version is v5.25.2 (Latest: v5.25.2)

Platform

  • OS and version:
    Debian 11 / VM/VPS
  • Platform:
    Proxmox

Expected behavior

 Client devices automatically get assigned an IP address from the defined pool of addresses.

Actual behavior / bug

 Client devices DO NOT receive a response from the PiHole/DCHP Server with a designated IP address for the device from the Address Pool.

Steps to reproduce

 Pihole -up

Debug Token

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

@boscorelly
Copy link

boscorelly commented Aug 4, 2024

hi, i confirm the same problem here.

docker version 2024.7.0 / 5.18.3.

from debug :

-rw-r--r-- 1 1000 pihole 790 Aug 4 23:18 /etc/dnsmasq.d/04-pihole-static-dhcp.conf
dhcp-host=04:CF:8C:41:D7:1C,192.168.1.150,Ventilateur-chambre

in pihole :

docker exec pihole cat /etc/pihole/dhcp.leases
1723064066 04:cf:8c:41:d7:1c 192.168.1.102 dmaker-fan-p5_miapD71C *

@boscorelly
Copy link

found my issue : as i use docker and needed a way to accept connections with external ip address, i added a route causing problems. remobing the route solved the problem.

Copy link

github-actions bot commented Sep 4, 2024

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.

@github-actions github-actions bot added the stale label Sep 4, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@boscorelly @angeloluidens and others