fcc821fc

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

The static leases belong with the reset, not after it

A NAS came up on 192.168.88.8 during a deployment and kept it, though the
configuration gives it a static lease. The reason is in the split: the
prefix ended at /ip dhcp-server network, so for the two minutes between the
reset and the import the router was running a dhcp server with no static
leases at all, handing out pool addresses to anything that asked. With
lease-time=30m, whatever asked kept the wrong address for half an hour.

Renewing at the end cannot fix that: RouterOS cannot make a client renew,
and removing a dynamic lease does not tell the client either.

So the line the router is reachable again from is now past the last static
lease as well as past the last required piece. A dhcp server is one of
those pieces, and a dhcp server without the leases it is meant to hand out
is one that hands out something else.

Both the split and the check for fallible commands before that line read
it from the same place now, since they were computing it separately and
would have disagreed.