Right, so DHCP is sitting there allocating IP addresses from the pool.
It starts at .200 and slowly works it’s way down to .1
On any given day .20, .75, .125 and .195 could be logged in.
Eventually it’s going to allocate the .1 IP address. What happens then?
Does DHCP start at .200 and allocate addresses that haven’t been used in a while, or what?
Is there a way to flush the DHCP and get it to start allocating IP addresses at the beginning of the scope again?
/ip dhcp-server lease remove
Yes, kind of. I think the default is 3days, after which clients lose their ip and that ip gets reassigned to the next requesting client. However, if you have 200+ clients coming onboard within this default period, then you’re going to run into issues.
You may decide to shorten the dhcp lease time. But I think a better approach would be to segment your network - introduce a ‘wider’ (e.g. /16) subnet to give you some extra ip addresses.
Thanks emeimi,
There are never more than 15 addresses allocated at the same time.
I still don’t understand why it is that each time a MAC address logs in after the lease has expired, it gets allocated a different IP address.
Then there’s the issue of why the DHCP server doesn’t re-allocate an address once it’s expired. Anyway, I’m about to reach “1” on the machine in question, so it’ll either start at 200 again (which was last allocated in March of this year), or I’ll be getting calls from users wanting to know why they can’t connect to the interwebthingie.
all will work fine. if you want details - as far as I remember, it will begin from .1 and up ))) I don’t know why 