I’m getting multiple error messages in the logs of one of my mikrotik routers. Here’s the error message:
18:15:45 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:15:51 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:00 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:02 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:02 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:04 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:11 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:12 system,info,account user admin logged in from 63.199.231.88 via
telnet
18:16:19 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
18:16:21 dhcp,error,warning,info,debug Phonecians: failed to give out IP
address: pool is empty
And like the error message says the client is not getting an IP address from the DHCP server. Currently I’m running RouterOS v.2.9.8 I’m in the process of upgrading to 2.9.10 while I’m writing this, maybe that will resolve the problem, however I didn’t see anything in the change logs so I’m posting this. The only way I can get this error message to go away is to delete/recreate the pool, then a few hours later I get the same errors filling up my log…
Here’s a synapsis of the situtation…
I have a x86 based mikrotik that has been running great for over a year. Its installed in a Multi Dwelling Unit (MDU) where customers are authenticated via MAC address. Previously when the box was running 2.8.23, I had mangle rules to authenticate users via MAC Address. After upgrading to 2.9.xx I’ve switched over to using the hotspot to authenticate users via MAC Address. All that seems to be working fine, but now out the blue the DHCP server has started kicking back these errors.. Any suggestions are appreciated. Hopefully the upgrade to 2.9.10 addresses the issue at hand.
thanks,
bill[/code]