Somehow I never noticed before that part of the problem stays with regard to the wifi devices.
I therefore run a 2nd command for that as well
This is what I have now in my crontab:
Code:
20 */4 * * * /usr/bin/ctlmgr_ctl w landevice command/cleanup_landevices 1
20 */4 * * * /usr/bin/ctlmgr_ctl w landevice command/cleanup_wifidevices 1
I hope this helps others.
EDIT:
It seems the latter (
/usr/bin/ctlmgr_ctl w landevice command/cleanup_wifidevices 1) is
not the right command after all. None of my WiFi-clients are gone, although I thought they did.
They must have reacted to the WebIF.
@PeterPawn I think you know what command is executed when "remove" is pressed in WiFi. I would really like to have that command and maybe also some info how to find such things by myself in the future...
It turns out I'm still getting problems that DHCP-clients are not getting a lease.
The file
/var/flash/multid.leases isn't cleaned by AVM's script either.
I just changed the subnetmask to
255.255.254.0 and changed the DHCP-pool to
192.168.178.20 ~ 192.168.179.250 in the hope that it doesn't happen too often.
Only after running my script and also rebooting the router enabled this.
I may need to put that tidy_ar7 script again in my cronjob.
Maybe with the help of the 2 other cronjobs it will not bring my Fritzbox to factory default again.
The last year I only used it manually several times and it never gave me troubles again...
Why on earth AVM has created a DHCP-server that can't do basic housekeeping is beyond me. It's not as if a DHCP-server is some new concept. It's been around us since 1993 (
I would have guessed even longer).