One three different hotspot setups i have im getting this message after a few weeks.

I run hotspot and a dhcp server to hand out a private IP. it also uses radius for authentication but that does not affect this.

if i do:

/ip pool used print

I will see maybe 30 used IP address, but my pool is 200.

Even a reboot will not fix it. the only solution i have found is to delete the dhcp server and pool and remake them.

two are running 2.9.40 and one 2.9.38. both rb 133s that run great otherwise

tks

Fix what? Your IP pool may have 200 addresses available, but it only issues what it needs as they are asked for by your clients. Mine is pretty smart. It keeps issuing me the same IP every time I manually renew it. It releases them back to the pool after three days.

/ip pool used print
shows only IPs issued and the MAC address of the network card it was issued to. So I will guess 30 computers have connected to your AP in the last 3 days.

Do you feel it is malfunctioning? If so, be a little more specific about the symptoms of the malfunction. What I I mean is: failing to run out of IPs is not a bad failure as I see it!

If this is the first time you have seen a dhcp server at work, they normally issue IPs from the top down. So what we would see as the "last IP" is the first issued.

Im getting this in the logs after the "hotspot new host detected"

"Failed to get IP adderss Pool Empty"

and im assuming at this point an ip address is *NOT* handed out to the newly detected host which is why im getting connectivity complaints from customers.

normally this is how the log looks for a new hotspot client (line two will not say added, but failed to get IP address, pool empty):

My bad! I see now. "Failed to get address. Pool empty". It is telling you the pool is empty and you think it isn't. Check
/ip hotspot print
and see what IP pool your hotspot is using. Then
/ip pool print
and see if that pool is there, and all is set ok. Especially the ranges. It should be:
192.168.0.2-192.168.0.253
if you selected the default setting.

Also check your IP assignment on your hotspot interface. Should be 192.168.0.1/24

EDIT: My apology, jo2jo. Didn't mean to sound patronizing. I missed the part about it working for a while, and the fact you appear not to be a newbie.

thanks for your help, but those are all basic things that have never been wrong or these hot spots would not have been working for the past year as they have.
the ip of the mt is 192.168.20.1
the pool is 192.168.20.100-230

I have had this problem and the solution for me, was to set -> ip -> hotspot -> servers tab-> server -> set idle time out to 00:05:00. the address poll emptied straightaway down to the addresses only in use. i hope someone else can use this information and avoid unnecessary stress.
Cheers Paul

Hi people IM new ,and they call me Gary.

Just being working today on similar problem at hotel, ip pool empty but only 2 users on , yet all the leases say busy , even if you check status. they all slowly come back busy. and tie up the ip pool .
Well after 9 coffies and checking and re checking i found what worked for me .

Under DHCP- in the authoritative set it to 10 seconds ,
I read about this authoritative thing from another member on this forum (thank you to them for pointing me in the right direction).

the yes setting did not work
the 2 seconds did not work
but the 10 seconds did like a charm

Mby if it dosent get a response time in an allocated time it drops it ?
I notice that when watching the leases in the DHCP a guest would log on and it would offer the IP then test the IP then drop it and set it to busy with a one hour count down.


Hope this helps some one. (mabye some talented person could explain the above better for us)

Cheers Gary (NZ)