I have a 911G-5HPnD on a clients roof, handing out an IP address via DHCP to the client’s router. The DHCP network uses a /30 subnet, therefore there is only one available IP address to hand out (the other is the Gateway on our 911).
What will happen is, the client will plug a different device into our line, and it will not pull an IP address because the pool is empty. This is to be expected, yes, but it seems the only way for the previous DHCP Lease to go away is for me to log into the radio and manually remove it (or let the lease time run out). Rebooting does not work.
I’m looking for a way to automatically clear the DHCP Leases upon a reboot. I tried ip dhcp-server config set store-leases-disk=never and it didn’t seem to work.
Perhaps there is a simple script to achieve what I’m looking for? That, or any other suggestions, would be much appreciated.
That doesn’t seem to be best practices. You can’t set a DHCP lease on an active network to 15 seconds.
Are you telling me there is no way to flush DHCP leases in Mikrotik???
Although I’m sure this does work, it’s hardly simple. It still doesn’t answer the question as to why there’s no way to flush DHCP leases. That seems like such a basic feature that ALL DHCP servers should have. I’m looking for ONE button that says “Flush DHCP Leases”. MT should have that.
And even after I removed all the leases manually, they were still active and passing traffic, not pulling a new DHCP lease.
The following list gives design goals specific to the transmission of
the network layer parameters. DHCP must:
o Guarantee that any specific network address will not be in
use by more than one DHCP client at a time,
o Retain DHCP client configuration across DHCP client reboot. A
DHCP client should, whenever possible, be assigned the same
configuration parameters (e.g., network address) in response
to each request,
o Retain DHCP client configuration across server reboots, and,
whenever possible, a DHCP client should be assigned the same
configuration parameters despite restarts of the DHCP mechanism,
Great that hits one of your gripes. To be a RFC compliant DHCP server they must be able to retain DHCP client configuration (read lease) across server (read your mikrotik) reboots. Ker-blamo.
The next item. How would a client know that the lease has been deleted on the server? The DHCP client on the PC is not listening for updates from the server and the server is not permitted to send updates to the PC unless it is part of the negotiation initiated by the server. The DHCPRELEASE message is a client issued packet and therefore can’t be sent by the server to the client. So that knocks out your other issue.
In other words, “working as intended.”
Now I get your problem, you’ve got a user and they just want an IP. They don’t care that they’ve been given a /30 and what not so I’m in favor you manually doing what you’ve got to do w/the DHCP lease on reboot.
An alternative solution might be to leverage the MikroTik API and script the removal of the lease in either your NMS, networking monitoring system, or your client portal. Let the customer login and click the “clear leases” button if they need to.