Help: Possible DHCP limit?

Hi,

I have a router Mikrotik RB1100 running a big hotel (300 beds) and some users reported problems to connect.
The Mikrotik is running a DHCP server with the network 192.168.8.0/22 (Lease Time is 3 hours) so the range should be big enough for everyone.
I was keeping an eye on the ‘Leases’ tab of the DHCP Server to see the connections and I noticed that the total list is always around 91 items so I’m afraid I may be missing something and limiting the IPs somewhere else?
The pool used by the DHCP is 192.168.8.2-192.168.11.254 and in the ‘Used Addresses’ I also see 91 items and it was like this for a long time…
Is it possible to know if the DHCP server is declining IPs to clients? Can it be limited somewhere else?
Thanks a lot!!

DHCP lease info is usually displayed in the log by default. Have you taken a look there? Perhaps you can turn on debugging for DHCP in the log and get a bit more info there. Only other thing I can think of off hand that might be limiting the clients is if you have your Max Station Count set really low in your WLAN interface settings.

Have you tried increasing the IP pool to see if it will let more than 91 clients on? Any trouble connecting yourself?

It could be a lot of things..

Error with configuration, rogue dhcp server or some other kind of delay, low throughput etc.
Of course first thing is to make sure you have the latest version of ROS.

What is exactly the problem reported? Have you seen it yourself?

They cannot connect at all? They do not get IP? They do not get correct IP?
If they can connect and get correct IP, then can they resolve dns names?

Sometimes it happens that due to delays with the network or low signal it takes too long to receive an IP address, the customer just has to reconnect.

I would suggest to take a closer look by yourself the next time you get a complain.
Also it would be a good idea to enable alerts for rogue dhcp servers in \ip dhcp-server alert.

RB1100 does not really have an issue with that amount of guest devices.

Thanks for your answers, I was in the place today and looks like the problem is with a couple of AP that are not working very well and it wasn’t in the router :slight_smile: