DHCP suddenly stopped working on VLAN/Subnets

Started by TheRealBeltet, November 15, 2021, 02:36:19 PM

Previous topic - Next topic
Hi! As the title says the DHCP servers on my subnets/vlans(all of them) have stopped working since yesterday.
I've tried with:
Removing all firewall rules
Recreate subnet/vlan.
Reverting to an older config.
Reinstalling the whole OS, and load saved config.
Tried to manual assign ip adress on clients(no connection anyway)

But to no avail.... Anyone have a idea what the problem can be? I cant see that I have configured something wrong... And the problem appeared from nowhere. I did not upgrade it or anything.
The only thing I know I did just before was rebooting pihole, But I have removed it as DNS on all networks.

The main network works as it should. But all subnets/vlans is broken.

The problem could be a little clearer.
What is not working exactly? Are the DHCP service logs showing errors, failing to start, stopping at some point?
Are the clients getting a lease, what are their logs showing?
What is your setup like? Like the LAN setup ipv4.
Just too much to consider to venture a guess from this report.

Quote from: cookiemonster on November 15, 2021, 05:22:40 PM
The problem could be a little clearer.
What is not working exactly? Are the DHCP service logs showing errors, failing to start, stopping at some point?
Are the clients getting a lease, what are their logs showing?
What is your setup like? Like the LAN setup ipv4.
Just too much to consider to venture a guess from this report.

What were not working was the assignment of IP adresses, so I could not get any network at all. Only on the main network, not on any subnetworks.
I could not see anything in the logs that could be related to the problem. I didn't even see any mention of the subnetworks.
The clients did not get any leases on the subnetworks.
But now the problem have been identified. It was my switch, somehow it started to block the connection on the subnetworks. I had not change any settings on it or even done something related to it.
But with a restore and a little bit of config it all works ok now.