Re: dnsmasq dhcp failure
Andrew <[email protected]> Fri, 14 Oct 2022 11:41:17 +0300
| Newsgroups | gmane.linux.leaf.user |
|---|---|
| Message-ID | <[email protected]> |
14.10.2022 01:24, Erich Titl пишет: > Hi Folks > > Am 13.10.2022 um 22:12 schrieb Andrew: >> 13.10.2022 20:16, Steve Tell пишет: >>> >>> ... >>> >>> A mechanism to automaticly restart daemons that exit would be nice. >>> But its not worth converting to systemd just for that - or at least >>> I'm not offering to do the work :-) > > I am not even sure how systemd could detect such a failure. > >> >> >> there's monit in packages for that purpose > > When using monit, how can monit detect that dnsmasq is not responding > to dhcp requests as the process appears to still be running, maybe not > running completely. So one would have to write something that detects > the non functionality. I have not found anything in the logs that > would suggest such a failure. It just appears as if the dhcp requests > are dropped, not in iptables but just like it gets digested inside > dnsmasq and not reacted to. > > It would be different if this was the DNS caching part of dnsmasq. But > then, to be honest, I hasve not even looked at this as a client > becomes nonfunctional if it cannot get an IP address. > > cheers > > ET monit can run external command or script. for ex., something like 'ip n|grep 192\.168\.0 | wc -l' (but it needs to have at least 1 client active), or compare iptables packes counter for 2 rules (input/output) for DHCP. ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/