I can access my pihole at http://192.168.1.101/admin/
I set pihole as DHCP server like this:
Range from 192.168.1.101 to 192.168.1.201
Gateway is my ISP modem : 192.168.1.254
I reboot my Raspberry and my ISP modem.
My problem is that I don't get knew IPs for most of my devices (maybe I should reboot them ?), but mostly I get new IPs for my other devices in the 192.168.0.x subnet and not 192.168.1.x as I asked for in my config. It messes up everything of course.
Here's an ugly diagram of my network if that helps. I'm not sure my router and switch can be a problem.
I SSH and work from my computer in "office 1".
Your Pi-hole's subnet is different from the one your router is using.
What's the motivation for that?
What's the machine at 192.168.1.254 that you've configured to be used as a gateway? Does that connect to your router on your 192.168.0.0/24 network, or is that a separate router providing its own internet connection?
There's no motivation for that. That's the issue. I want everyone in the same subnet.
192.168.1.254 is my ISP modem. It connects to my router that connects to my switch that connects my Raspberry. Please, have a look at my ugly diagram. It displays all the setup and current IPs for my main devices.
Never have I ever asked for something to be in 192.168.0.0/24 network.
My computer and some android devices get IPs in the 192.168.0.0/24 network. I don't know nor understand why ?! And at the same time, the other devices stay in the IP range attributed by my ISP modem (meaning 192.168.1.1 to 192.168.1.100 and not 192.168.1.101 to 192.168.1.201 as configured in pihole DHCP) while DHCP IS disabled on my ISP modem.
What IP range did you configure for Pi-hole's DHCP server?
Which machine is handling DHCP in your network up to now?
The following may help answering that question:
pihole-FTL dhcp-discover
Note that a DHCP client may pick any DHCP server answering its broadcast to acquire a DHCP lease (so Pi-hole as well as an existing DHCP server).
Furthermore, a client with an existing lease would continue to talk to the DHCP server it acquired its lease through. If that's your current DHCP server and it's still active, that client may never ask your Pi-hole for a lease - unless you disconnect it from the network, e.g. by powercycling it.
If you do intend to keep that existing DHCP server running in addition to Pi-hole, you'd want to make sure that your DHCP servers IP ranges do not overlap, and you may want to use static leases / DHCP lease reservation for all of its intended clients.