@ryanrozich said in dhcpd.log file is ~10GB, filling my disk up every couple days and taking my network down:
from wired to wireless networking
That's original, as normally, it's the wireless connection that has a very limited (bad) connection, so it get reconstructed again and again, and that introduces a DHCP sequence on every 'link up'.
If a wired connection does this : I'll bet you have a bad NIC on one side, or a bad cable.
Or the printer has a very bad DHCP client implementation, like : forcing the the DHCP lease duration to 10 seconds or so.
@ryanrozich said in dhcpd.log file is ~10GB, filling my disk up every couple days and taking my network down:
However if this hadn’t taken down my home network I wouldn’t have known about it. Is there any alerting that I could enable in pfsense that would warn me of problems like this?
That is actually the reason why pfSense is not some AI driven device that you power up, hook up and walk away. Like a switch.
pfSense needs the human type of admin, in this case : you. And 99 % of the time you won't be looking at the dashboard, but you're somewhere in the Status menu.
The most favorite one is all the log files.
And no, I'm not kidding
But I have a tip : when you add a 'new' device to your network, you should have a look at your log files (System, DHCP, DNS) a couple of times.
Things can always go bad, cable get cut, wifi gets destroyed by the new AP the neighbor bought (or the new micro wave that "works just fine with the door open").
