please check this problem at times my clients have conflicting ips which have been issued by the mikrotik dhcp server and the clients end not browsing untill i reboot the mikrotik which is not good since at that time i have about 70 hotspot users and would not like to be interupted when i reboot the issue is resolved but another may experience same problem
Never seen such a problem. Anyway post router configuration and share ROS version. Without any additional information its impossible to check anything.
same has been raised in the forum will send the dhcp leases when the same happens
When it happens again make supout files, describe problem, include forum threads, and send it to support@mikrotik.com
Anything unusual setup? Any static dhcp leases? Radius ip assignments? Multiple dhcp severs on the network? Might want to print and post:
/ip dhcp-server
/ip dhcp-server lease
/ip pool
please have a look at the file attached you will find that the ip address 10.0.0.89 has been issued to a client as per the ip/hotspot/host. then when you look at the ip/dhcp-server/leases the same ip has been issued to a different client too
double issue of IP addresses.txt (34.8 KB)
There are a lot of entries there, but from what I see, the ip in the hotspot host list is a static assignment bypassed through the hotspot, not issued by dhcp. This one:
1 SP 00:15:E9:00:95:6F 10.0.0.89 10.0.0.89 hotspot1
Are you assigning static ips in the same range the dhcp server issues?
ADD: There is a difference between a static assignment and a static dhcp lease. If you used
/ip dhcp-server lease
make-static X
and THEN it assigned that ip to another mac address, that would be a bug.
the IP that is on the host list as 10.0.0.89 was assigned by the DHCP server then i made it static. But why would the DHCP server issue the same IP when in the Hotspot Host there is a machine/client with that IP address which itself it issued. Before the Dhcp server issues an ip address it checks if that particular ip is existing in the network if not then that is when it issues the IP. Definately this is a bug. Or how can we explain it ?
I don’t see a duplicate entry in the dhcp lease list. Just this one listing:
33 10.0.0.89 00:C0:CA:2F:3F:7C Aga dhcp1 bound
This appears to be the mac address you set to “make-static” for 10.0.0.89. This network card should be an ALFA product.
Are you sure that mac address in hotspot host list (00:15:E9:00:95:6F) is getting its ip by dhcp? It should be a D-Link product.
ADD: I would change the hotspot ip-binding to allow the mac address 00:C0:CA:2F:3F:7C to bypass rather than the ip address 10.0.0.89. I would also watch the hotspot host list for any other bypassed ips. If you get the same mac address picking up another bypassed ip, then you have a “connection hijacker”.
I missed your last question. The dhcp server checks the lease list only. How is it supposed to “check” for duplicate static ips? My firewall makes my computer “invisible” on the network.
00:15:E9:00:95:6F is a nanostation (Ubiquiti)
yes there is no duplicate listing but the fact that there are 2 units with the same IP address both issued by the same DHCP server on the mikrotik
I made the 00:15:E9:00:95:6F static after it was issued by the DHCP Server on the Mikrotik of which i do not expect the DHCP server to lease that IP again to another as it has been given out. Once made static it means it is not available for lease then how come it has been leased.
all my clients are on dhcp aprt from the other mikrotik routers and servers.
Before a DHCP server issues an IP address to a unit/machine it will check on the network to check if that IP exists on the network. I expect IP conflict where there are 2 DHCP servers on the same network with the same network range for thier pool of IP’s
00:15:E9:00:95:6F is a nanostation (Ubiquiti)
I do not see this mac address in your dhcp lease list. If there was a static dhcp lease for this mac address, it would look like this:
33 10.0.0.89 00:15:E9:00:95:6F Aga dhcp1 bound
Notice no ‘D’ after 33. The ‘D’ means a dynamic lease.
Am I missing it? What I see as a static lease in your list is what I posted above.
ADD: The nanostation is set up to be a dhcp client on this network, correct?
00:15:E9:00:95:6F is a nanostation (Ubiquiti)
This does not appear in the leases as it was issued earlier after which i ip-bound it with the Ip that was issued. So once it has been bound to that IP in ip-binding you will not see it in the leases when the unit is rebooted as the Leases will only show the freshly issued ip’s
the 10.0.0.89 00:15:E9:00:95:6F Aga dhcp1 bound was dynamic but once i made it static then the D disappears notice the dhcp1 which is the issuing dhcp server.
the 10.0.0.89 > 00:15:E9:00:95:6F > Aga dhcp1 bound was dynamic but once i made it static then the D disappears notice the dhcp1 which is the issuing dhcp server
No, that is what you wanted, not what was entered. This is what was entered:
33 10.0.0.89 00:C0:CA:2F:3F:7C Aga dhcp1 bound
This is NOT the same mac address! And the “bound” means this client is connected and assigned 10.0.0.89.
ADD: Maybe you should try renewing the dhcp lease on the nanostation. Do a reboot or ??
Unless you renew the lease at the nanostation after resetting the router, it may think it has a current 3 day lease on a now invalid ip.