One device is stuck in some kind of DHCP loop

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

The device should be connected to the network.

Actual Behaviour:

The device seems to be stuck in some kind of DHCP-loop. (This device got connected before I started to use pihole as DHCP and DNS)

Debug Token:

https://tricorder.pi-hole.net/msvensubx0

This is coming to the log like every minute.
May 30 17:17:59 dnsmasq-dhcp[17070]: DHCPDISCOVER(enxb827eb6e0639) xx:xx:xx:xx:xx:xx
May 30 17:17:59 dnsmasq-dhcp[17070]: DHCPOFFER(enxb827eb6e0639) 192.168.1.65 xx:xx:xx:xx:xx:xx
May 30 17:17:59 dnsmasq-dhcp[17070]: DHCPREQUEST(enxb827eb6e0639) 192.168.1.65 xx:xx:xx:xx:xx:xx
May 30 17:17:59 dnsmasq-dhcp[17070]: DHCPACK(enxb827eb6e0639) 192.168.1.65 xx:xx:xx:xx:xx:xx 2508576D621051F0

So just this device doesn't likes the pihole DHCP for some reason.

2

Is the device a Google device?

3

No... It's an air purifier from Blueair. Blueair Classic 480i.

I managed to get it connected, I added it to the "Static DHCP leases configuration" in Pi-Hole and after that it got IP and got connected to the network.

4

It's still weird tough... So en explination why it didn't work with the IP the DHCP tought the device should have would be cool =) Or did the device just hate that IP. :smiley: The IP the DHCP would give the device from start was 192.168.1.65 but then I give it 192.168.1.40 in the static configuration and it worked.

5

Ok... This is very weird, I powered of the device because I was going to move it to another room and after that I got this DHCP-loop again, and when I from the web interface removed the static DHCP and saved so pihole-FTL restarted the device got the IP from the DHCP-pool, the one that it didn't want before and it got it this time. Well, then I had to power of the device again, and when it started it was stuck in the DHCP-loop, så I added it to the static DHCP conf again with the same static IP as before and saved to pihole-FTL restarted and it went fine and got that IP. So this seems to be an error every time the device is power cycled and connects to the DHCP-server.

6

I don't think this is a Pi-Hole issue. The issue appears to be with the client.

7

I've seen this before with different devices that do not acknowledge the DHCP packet properly.

In order to avoid any DHCP related issues, set a fixed IP on the device ...

8

@jfb
Depends on how you look on it... Before I changed to Pi-Hole as DHCP and DNS and used my Edgerouter-X as this, it worked just fine.

9

I can't set a fixed IP on this device... But after I change from static or not static so there is another IP-adress the DHCP packet is alright of some weird reason. :slight_smile:

10

The DHCP functionality of Pi-Hole is part of the embedded dnsmasq and is not written by the Pi-Hole developers.

11

I think I will open a ticket with Blueair, because all other devices doesn't have any problem.

12

How do I know what version of dnsmasq Pi-Hole is running in the FTL?

13

dig chaos txt version.bind +short

2 Likes
14

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