The network overview page of the admin console appears to list the devices connected to the network being monitored by Pihole.
Some of the devices in my listing have two IPv4 addresses, some have one, one has three.
Can someone explain why there are multiple addresses?
Thanks.
If you have a short lease duration on your DHCP server, they can be getting a different IP fairly frequently.
Thanks, but I don't think lease duration (24 hours) is the reason because I have reserved IPs on the router for all connected devices. And the second IPs are widely separated from the reserved IPs. For instances, the reserved IP for one device is 192.168.1.111; the second (DHCP-assigned) IP listed in Pihole for that device is 192.168.1.227. That's just my thought.
Please post a screen capture of your network page - in this forum you can copy and paste an image directly into a reply.
Pi-hole gets the IPs of network clients partially from the neigh table, so you might also want to look at what's in there:
ip neigh
Something on your network must hand out these other reservations.
What router are you using?
By any chance: you've disabled pihole's DHCP server?
ADD
If you look at the hostnames I see two different local domains in your hostnames, *.lan and *.gci.net. Maybe this indicates two concurrent DHCP servers (or misconfiguration?)
Linksys WRT1900ACS.
I'm not using the pihole DHCP server. I'm using the router's DHCP server and assigned pihole as the router's DNS server. No other DHCP server; at least none that I can find.
Is it "better" to use the pihole server? Why?
Looks like it is a router issue:
They mention the "cloud" feautre, maybe you could try to disable it?
Not sure if "better", but might be worth a try if your router is the problem. It is for sure deterministic, handing out always the same IP to a client even without reservations.
I've enabled the Pihole DHCP server and assigned static leases to my connected devices. But the assignments are not being honored. One or more devices have IPs different from the assigned static IP.
If you disconnect (to renew the leases) a clients from the network and have them set to DHCP there is only one way how I could image this to happen - there is another active dhcp server on your network.
On a client with a "wrong" IP try (on windows)
ipconfig /all | find /i “DHCP Server”
or linux
sudo nmap --script broadcast-dhcp-discover -e eth0
Thanks, yubiuser!!
I think I've resolved the two DHCP server problem. Here's a recent network scan from pi-hole
Following the advice in your last post, I ran ipconfig on my laptop (192.168.1.101) and it correctly reported that 192.168.1.192 is the DHCP server. But pihole reports two additional IP addresses for the laptop: 192...198 and 192...201
Why is that happening??
And I ran the linux command on a linux machine (192.168.1.192) and got this result:
broadcast-dhcp-discover:
| Response 1 of 1:
| IP Offered: 192.168.1.215
| DHCP Message Type: DHCPOFFER
| Server Identifier: 192.168.1.192
| IP Address Lease Time: 2m00s
| Renewal Time Value: 1m00s
| Rebinding Time Value: 1m45s
| Subnet Mask: 255.255.255.0
| Broadcast Address: 192.168.1.255
| Domain Name Server: 192.168.1.192
| Domain Name: lan
|_ Router: 192.168.1.1
Where did the 192...215 IP address come from?
This is all very confusing. I feel like I'm in the deep end of the pool.
It was offered by a device with the IP
As it is the same as your DNS Server (Pihole?!)
I guess you enabled Pihole's DHCP server.
So I guess you run two DHCP servers: your router at 192.168.1.1. and pihole on 192.168.1.192.
You have to decide which one you want to disable...
But I disabled the router's DHCP server when I enabled the pihole server. And Fing indicates the existence of only one server.
Did you flush your network table after you did the switch? Maybe the table is still full of "old" entries. Try Settings/System/Flush network table and see if more than one IP gets assigned to the devices when pihole is the only DHCP server.
yubiuser--you are the man! Flushed and one problem solved.
Next problem: pihole isn't recognizing static lease assignments made in settings/DHCP
For instance, iphone-xsmax is assigned 192...111 but shows up as 192.105. Some, but not all, of the assignments are good.
The fastest way to acquire a new lease is to disconnect the device from the server and reconnect (turn wifi off/on). See if that helps.
Disconnect/reconnect isn't working. Still ignoring the static reservations set in pihole.
You might be affected by this.
Try the solutions proposed.
A post was split to a new topic: IP address question/problem
