Hotspot dhcp leases problem

RouterOS General
1

Strange situation with hotspot dhcp leases. May it be of weak wireless signal?
Looks like this:

11:35:59 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:35:59 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:01 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:02 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:04 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:05 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:07 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:08 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:09 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:10 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:12 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:13 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:15 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:16 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:18 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:19 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:20 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:21 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:23 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:24 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:26 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:27 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:29 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:30 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:32 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:33 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:34 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:35 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:37 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:38 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:40 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:41 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:43 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:44 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:45 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:46 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:48 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:49 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:51 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:52 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:54 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:55 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:57 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:36:58 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:36:59 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:37:00 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:37:02 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:37:03 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:37:05 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:37:06 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A 
11:37:08 dhcp,info dhcp2 assigned 192.168.0.5 to 00:23:4D:69:B2:4A 
11:37:08 dhcp,info dhcp2 deassigned 192.168.0.5 from 00:23:4D:69:B2:4A
2

That is normally not caused by weak signal. What is the lease time on that dhcp server?

/ip dhcp-server print

I have “donated” my router to the MikroTik devlopment team this morning for almost exactly the same dhcp server log entries.

3

Lease Time is 2 minutes.
Not all clients have this problem. So I thought about weak signal.
And then:

12:00:24 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:30 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:35 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:41 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:46 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:52 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:00:57 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:03 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:08 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:14 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:19 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:25 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:30 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:36 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:38 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:40 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:41 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C 
12:01:43 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:45 dhcp,warning dhcp2 offering lease 192.168.0.29 for 10:93:E9:0C:A9:7C without success 
12:01:45 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:46 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C 
12:01:48 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:49 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C 
12:01:51 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:52 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C 
12:01:54 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:55 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C 
12:01:56 dhcp,info dhcp2 assigned 192.168.0.29 to 10:93:E9:0C:A9:7C 
12:01:58 dhcp,info dhcp2 deassigned 192.168.0.29 from 10:93:E9:0C:A9:7C
4

By the log and the lease time, I say you have a different problem I have. Mine goes through that log entry stuff at exactly the lease time. Yours seems to be doing it every couple seconds. ??

Have you tried changing the lease time to 10 minutes?

5

Yeap, nothing changed ((
Maybe this is some dhcp timing problem.

6

Another user had about the same problem, but it was not every couple seconds. More like every 40 minutes.
http://forum.mikrotik.com/t/security-help-as-well-as-why-router-deassign-and-assign-ip/65654/1
The OP there had the lease time set to 3 days.

Mine is very particular about the device. Most dhcp clients do fine, but there are a few devices that cause a minor malfunction in the dhcp server data. My router’s dhcp server sends an ACK to the client with a successful renew, but doesn’t store the new lease time, so the lease expires prematurely.

I just heard my router reboot, so the MT development team must be checking my router now. Maybe that will shed some light on all this.

7

I have this problem on different devices x86 and mipsle.
And I have an idea, both devices have long ethernet line after hotspot vlan, some switches across the city.

8

According to MikroTik developers, the problem in my case is a faulty renewal packet from the client. I have not checked with the developers of the client equipment yet, but considering that most other clients do ok, that sounds about right.

The deassigned log messages are created when the dhcp server expires the current lease for that ip/mac address. Then your device is renewing it (or rebinding) a couple seconds later. That creates the assigned messages. Since the deassigned/assigned messages are happening back-to-back, it seems unlikely it is caused by a connection problem.

Wish I could be more help.

edit: I can be a little bit more help. You might try enabling verbose logging for the dhcp server.

/system logging
add topics=dhcp,debug action=memory

And check the lease in “/ip dhcp-server lease”, and see what the dhcp server is returning to the client, and what it is storing in its database.

/ip dhcp-server lease
print detail

Then watch the log for renewal requests, and see if the server is returning the correct Address-Time value. If you are set for 2 minutes, the server should send “Address-Time = 120”.

/log
print follow where topics~"dhcp"

The dhcp lease time is independent of the connection state. If the client shuts down his/her laptop, that does not expire the lease. It remains valid until the lease expires by time, so losing the connection will not generate a deassigned message in the log.

9

[youtube]
http://www.youtube.com/watch?v=zbBsB1xHbwU
[/youtube]
Lease Status looks very strange, it`s switching between offered/testing/bound

“Address-Time = 600” - 10m
Logs:

12:18:58 dhcp,debug,packet dhcp2 sending offer with id 2977399548 to 255.255.255.255 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     yiaddr = 192.168.0.5 
12:18:58 dhcp,debug,packet     siaddr = 10.0.36.254 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = offer 
12:18:58 dhcp,debug,packet     Server-Id = 10.0.36.254 
12:18:58 dhcp,debug,packet     Address-Time = 600 
12:18:58 dhcp,debug,packet     Subnet-Mask = 255.255.252.0 
12:18:58 dhcp,debug,packet     Router = 192.168.3.254 
12:18:58 dhcp,debug,packet     Domain-Server = 8.8.8.8 
12:18:58 dhcp,debug,packet dhcp2 received discover with id 1150170440 from 0.0.0.0 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = discover 
12:18:58 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:58 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:58 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:58 dhcp,debug,packet dhcp2 sending offer with id 1150170440 to 255.255.255.255 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     yiaddr = 192.168.0.5 
12:18:58 dhcp,debug,packet     siaddr = 10.0.36.254 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = offer 
12:18:58 dhcp,debug,packet     Server-Id = 10.0.36.254 
12:18:58 dhcp,debug,packet     Address-Time = 600 
12:18:58 dhcp,debug,packet     Subnet-Mask = 255.255.252.0 
12:18:58 dhcp,debug,packet     Router = 192.168.3.254 
12:18:58 dhcp,debug,packet     Domain-Server = 8.8.8.8 
12:18:58 dhcp,debug,packet dhcp2 received request with id 1965371518 from 0.0.0.0 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = request 
12:18:58 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:58 dhcp,debug,packet     Address-Request = 192.168.0.5 
12:18:58 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Unknown(81) = 00-00-00-80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:58 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:58 dhcp,debug,packet dhcp2 sending nak with id 1965371518 to 255.255.255.255 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = nak 
12:18:58 dhcp,debug,packet     Server-Id = 10.0.36.254 
12:18:58 dhcp,debug,packet dhcp2 received request with id 1320430689 from 0.0.0.0 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = request 
12:18:58 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:58 dhcp,debug,packet     Address-Request = 192.168.0.5 
12:18:58 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Unknown(81) = 00-00-00-80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:58 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:58 dhcp,debug,packet dhcp2 received discover with id 2600549995 from 0.0.0.0 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = discover 
12:18:58 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:58 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:58 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:58 dhcp,debug,packet dhcp2 received request with id 2578439755 from 0.0.0.0 
12:18:58 dhcp,debug,packet     flags = broadcast 
12:18:58 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:58 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:58 dhcp,debug,packet     Msg-Type = request 
12:18:58 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:58 dhcp,debug,packet     Address-Request = 192.168.0.5 
12:18:58 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Unknown(81) = 00-00-00-80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:58 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:58 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:59 dhcp,debug,packet dhcp2 received discover with id 3415879015 from 0.0.0.0 
12:18:59 dhcp,debug,packet     flags = broadcast 
12:18:59 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:59 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:59 dhcp,debug,packet     Msg-Type = discover 
12:18:59 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:59 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:59 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:59 dhcp,debug,packet dhcp2 received request with id 3415879015 from 0.0.0.0 
12:18:59 dhcp,debug,packet     flags = broadcast 
12:18:59 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:59 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:59 dhcp,debug,packet     Msg-Type = request 
12:18:59 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:59 dhcp,debug,packet     Address-Request = 192.168.0.5 
12:18:59 dhcp,debug,packet     Server-Id = 10.0.36.254 
12:18:59 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Unknown(81) = 00-00-00-80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:59 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:59 dhcp,debug,packet dhcp2 received discover with id 2255180796 from 0.0.0.0 
12:18:59 dhcp,debug,packet     flags = broadcast 
12:18:59 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:59 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:59 dhcp,debug,packet     Msg-Type = discover 
12:18:59 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:59 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:59 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific 
12:18:59 dhcp,debug,packet dhcp2 received request with id 2908702462 from 0.0.0.0 
12:18:59 dhcp,debug,packet     flags = broadcast 
12:18:59 dhcp,debug,packet     ciaddr = 0.0.0.0 
12:18:59 dhcp,debug,packet     chaddr = E8:03:9A:CE:8D:D5 
12:18:59 dhcp,debug,packet     Msg-Type = request 
12:18:59 dhcp,debug,packet     Client-Id = 01-E8-03-9A-CE-8D-D5 
12:18:59 dhcp,debug,packet     Address-Request = 192.168.0.10 
12:18:59 dhcp,debug,packet     Host-Name = 80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Unknown(81) = 00-00-00-80-AB-A5-AA-E1-A0-AD-A4-E0-2D-8F-8A 
12:18:59 dhcp,debug,packet     Class-Id = "MSFT 5.0" 
12:18:59 dhcp,debug,packet     Parameter-List = Subnet-Mask,Domain-Name,Router,Domain-Server,NETBIOS-Name-Server,Unknown(46
),Unknown(47),Unknown(31),Static-Route,Classless-Route,MS-Classless-Route,Vendor-Specific

/ip dhcp-server lease print detail

address=192.168.0.13 mac-address=E8:03:9A:CE:8D:D5 
     client-id="1:e8:3:9a:ce:8d:d5" server=dhcp2 dhcp-option="" status=testing 
     expires-after=0s last-seen=0s active-address=192.168.0.13 
     active-mac-address=E8:03:9A:CE:8D:D5 active-client-id="1:e8:3:9a:ce:8d:d5" 
     active-server=dhcp2 host-name="\80\AB\A5\AA\E1\A0\AD\A4\E0-\8F\8A"

or

address=192.168.0.13 mac-address=E8:03:9A:CE:8D:D5 
     client-id="1:e8:3:9a:ce:8d:d5" server=dhcp2 always-broadcast=yes 
     dhcp-option="" status=offered expires-after=28s last-seen=2s 
     active-address=192.168.0.13 active-mac-address=E8:03:9A:CE:8D:D5 
     active-client-id="1:e8:3:9a:ce:8d:d5" active-server=dhcp2 
     host-name="\80\AB\A5\AA\E1\A0\AD\A4\E0-\8F\8A"

or

address=192.168.0.14 mac-address=E8:03:9A:CE:8D:D5 
     client-id="1:e8:3:9a:ce:8d:d5" server=dhcp2 dhcp-option="" status=bound 
     expires-after=10m last-seen=0s active-address=192.168.0.14 
     active-mac-address=E8:03:9A:CE:8D:D5 active-client-id="1:e8:3:9a:ce:8d:d5" 
     active-server=dhcp2 host-name="\80\AB\A5\AA\E1\A0\AD\A4\E0-\8F\8A"

and then again …

10

12:18:58 dhcp,debug,packet dhcp2 sending nak with id 1965371518 to 255.255.255.255

Something is not right there. How do the leases look in “/ip dhcp-server lease”?

/ip dhcp-server lease
print detail

Do the values for “last-seen” and “expires-after” look normal for other leases? If you add those values, they should total the lease time.

edit: The nack was apparently caused by the client asking for an unavailable ip. The ip it requested is not the ip it is eventually assigned.

Check “/ip hotspot host”. Is there a NAT being performed on that ip/mac address?

/ip hotspot host print
11 
Flags: X - disabled, R - radius, D - dynamic, B - blocked 
 0 D address=192.168.0.3 mac-address=18:F4:6A:31:29:7A server=dhcp2 
     dhcp-option="" status=bound expires-after=7m38s last-seen=2m22s 
     active-address=192.168.0.3 active-mac-address=18:F4:6A:31:29:7A 
     active-server=dhcp2 host-name="padmin-Aspire-4820TG" 

 1 D address=192.168.0.5 mac-address=00:C0:CA:66:03:3E 
     client-id="1:0:c0:ca:66:3:3e" server=dhcp2 dhcp-option="" status=bound 
     expires-after=9m last-seen=1m active-address=192.168.0.5 
     active-mac-address=00:C0:CA:66:03:3E active-client-id="1:0:c0:ca:66:3:3e" 
     active-server=dhcp2 host-name="Karina" 

 2 D address=192.168.0.18 mac-address=48:DC:FB:6C:18:B5 
     client-id="1:48:dc:fb:6c:18:b5" server=dhcp2 dhcp-option="" status=bound 
     expires-after=7m54s last-seen=1s active-address=192.168.0.18 
     active-mac-address=48:DC:FB:6C:18:B5 
     active-client-id="1:48:dc:fb:6c:18:b5" active-server=dhcp2 

 3 D address=192.168.0.6 mac-address=6C:83:36:F6:CC:D0 
     client-id="1:6c:83:36:f6:cc:d0" server=dhcp2 dhcp-option="" status=offered 
     expires-after=29s last-seen=1s active-address=192.168.0.6 
     active-mac-address=6C:83:36:F6:CC:D0 
     active-client-id="1:6c:83:36:f6:cc:d0" active-server=dhcp2 
     host-name="GT-S5380D" 

 4 D address=192.168.0.10 mac-address=E8:03:9A:CE:8D:D5 
     client-id="1:e8:3:9a:ce:8d:d5" server=dhcp2 dhcp-option="" status=testing 
     expires-after=0s last-seen=0s active-address=192.168.0.10 
     active-mac-address=E8:03:9A:CE:8D:D5 active-client-id="1:e8:3:9a:ce:8d:d5" 
     active-server=dhcp2 host-name="\80\AB\A5\AA\E1\A0\AD\A4\E0-\8F\8A"

looks good

/ip hotspot host print
Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed 
 #    MAC-ADDRESS       ADDRESS         TO-ADDRESS      SERVER       IDLE-TIMEOUT
 0  P ;;; 
      00:1C:10:66:ED:EA 10.0.36.42      10.0.36.42      hs-bridge1   10m         
 1  P ;;; 
      00:0C:42:E1:82:A4 10.0.36.75      10.0.36.75      hs-bridge1   10m         
 2  P ;;; 
      00:1C:10:66:E6:F1 10.0.36.41      10.0.36.41      hs-bridge1   10m         
 3 HA 18:F4:6A:31:29:7A 192.168.0.3     192.168.0.3     hs-bridge1  
 4 H  00:C0:CA:66:03:3E 192.168.0.5     192.168.0.5     hs-bridge1   10m         
 5 D  E8:03:9A:CE:8D:D5 192.168.0.9     192.168.0.9     hs-bridge1   10m         
 6 HA 48:DC:FB:6C:18:B5 192.168.0.18    192.168.0.18    hs-bridge1

Yeap, NAT is present.

Edit:

4 H  00:C0:CA:66:03:3E 192.168.0.5     192.168.0.5     hs-bridge1                                   10m         
 5 D  E8:03:9A:CE:8D:D5 192.168.0.13    192.168.0.13    hs-bridge1                                   10m         
 6 D  F4:EC:38:A8:43:C8 10.0.36.90      192.168.0.11    hs-bridge1                                   10m         
 7 H  64:A7:69:7B:1C:DC 192.168.0.14    192.168.0.14    hs-bridge1                                   10m         
 8 D  E8:03:9A:CE:8D:D5 192.168.0.16    192.168.0.1     hs-bridge1                                   10m

this mac (E8:03:9A:CE:8D:D5) have 2 records .. strange

Edit:
It`s a public Hotspot Router

12

Two records and 3 ip addresses.
192.168.0.13
192.168.0.16
192.168.0.1

I don’t know about “looks good”. Looks like mine in a way. Most have the correct values, but a few don’t, like this entry. Do those two values add up to 10 minutes? My addition totals 7m55s

2 D address=192.168.0.18 mac-address=48:DC:FB:6C:18:B5
client-id=“1:48:dc:fb:6c:18:b5” server=dhcp2 dhcp-option=“” status=bound
expires-after=7m54s last-seen=1s > active-address=192.168.0.18
active-mac-address=48:DC:FB:6C:18:B5
active-client-id=“1:48:dc:fb:6c:18:b5” active-server=dhcp2

edit: How many leases do you have in your lease list? I don’t know how you have your network set, but if the dhcp server works like mine, it issues top down, and 192.168.0.1 would be the last ip issued before it runs out of ips in the address pool.

That lease above may be about correct if the lease time is 2 minutes, and it has renewed twice (every minute) and the “expires-after” was not updated if the dhcp server thinks the lease is for 10 minutes.

I’m not sure how you are getting 10 minute leases with the lease time set to 2 minutes. Maybe there is a minimum lease time of 10 minutes?

13

Yes, you are right. Some leases is good some is not.
Address pool is 192.168.0.1 - 192.168.3.253
So pool is not empty.

This is all leases for the moment:

Flags: X - disabled, R - radius, D - dynamic, B - blocked 
 0 D address=192.168.0.13 mac-address=18:F4:6A:31:29:7A server=dhcp2 dhcp-option="" status=bound 
     expires-after=8m48s last-seen=1m12s active-address=192.168.0.13 active-mac-address=18:F4:6A:31:29:7A 
     active-server=dhcp2 host-name="padmin-Aspire-4820TG" 

 1 D address=192.168.0.7 mac-address=64:A7:69:7B:1C:DC server=dhcp2 always-broadcast=yes dhcp-option="" 
     status=offered expires-after=29s last-seen=1s active-address=192.168.0.7 
     active-mac-address=64:A7:69:7B:1C:DC active-server=dhcp2 host-name="android_25b25e6365c0351e" 

 2 D address=192.168.0.21 mac-address=18:F4:6A:13:43:E8 client-id="1:18:f4:6a:13:43:e8" server=dhcp2 
     dhcp-option="" status=bound expires-after=5m20s last-seen=4m40s active-address=192.168.0.21 
     active-mac-address=18:F4:6A:13:43:E8 active-client-id="1:18:f4:6a:13:43:e8" active-server=dhcp2 
     host-name="Admin-PC" 

 3 D address=192.168.0.12 mac-address=DC:85:DE:22:B5:85 client-id="1:dc:85:de:22:b5:85" server=dhcp2 
     always-broadcast=yes dhcp-option="" status=bound expires-after=5m1s last-seen=4m59s 
     active-address=192.168.0.12 active-mac-address=DC:85:DE:22:B5:85 
     active-client-id="1:dc:85:de:22:b5:85" active-server=dhcp2 host-name="v" 

 4 D address=192.168.0.24 mac-address=6C:F3:73:06:60:5A client-id="1:6c:f3:73:6:60:5a" server=dhcp2 
     dhcp-option="" status=bound expires-after=9m19s last-seen=41s active-address=192.168.0.24 
     active-mac-address=6C:F3:73:06:60:5A active-client-id="1:6c:f3:73:6:60:5a" active-server=dhcp2 
     host-name="android-1658f21806bf4aa0" 

 5 D address=192.168.0.22 mac-address=0C:14:20:85:B1:F3 client-id="1:c:14:20:85:b1:f3" server=dhcp2 
     dhcp-option="" status=bound expires-after=3m41s last-seen=6m19s active-address=192.168.0.22 
     active-mac-address=0C:14:20:85:B1:F3 active-client-id="1:c:14:20:85:b1:f3" active-server=dhcp2 
     host-name="android-45a32c3e60af90ff" 

 6 D address=192.168.0.18 mac-address=14:F4:2A:6E:82:7C client-id="1:14:f4:2a:6e:82:7c" server=dhcp2 
     dhcp-option="" status=bound expires-after=9m56s last-seen=4s active-address=192.168.0.18 
     active-mac-address=14:F4:2A:6E:82:7C active-client-id="1:14:f4:2a:6e:82:7c" active-server=dhcp2 

 7 D address=192.168.0.10 mac-address=00:F4:B9:24:56:58 client-id="1:0:f4:b9:24:56:58" server=dhcp2 
     always-broadcast=yes dhcp-option="" status=bound expires-after=7m50s last-seen=2m10s 
     active-address=192.168.0.10 active-mac-address=00:F4:B9:24:56:58 active-client-id="1:0:f4:b9:24:56:58" 
     active-server=dhcp2 host-name="Kamillas-iPhone" 

 8 D address=192.168.0.2 mac-address=F4:F1:5A:3D:3E:D5 client-id="1:f4:f1:5a:3d:3e:d5" server=dhcp2 
     dhcp-option="" status=bound expires-after=6m18s last-seen=3m42s active-address=192.168.0.2 
     active-mac-address=F4:F1:5A:3D:3E:D5 active-client-id="1:f4:f1:5a:3d:3e:d5" active-server=dhcp2 
     host-name="Ayhan-iPhoneu" 

 9 D address=192.168.0.36 mac-address=D0:DF:C7:03:20:F0 client-id="1:d0:df:c7:3:20:f0" server=dhcp2 
     dhcp-option="" status=offered expires-after=26s last-seen=4s active-address=192.168.0.36 
     active-mac-address=D0:DF:C7:03:20:F0 active-client-id="1:d0:df:c7:3:20:f0" active-server=dhcp2 

10 D address=192.168.0.23 mac-address=00:24:D6:4A:3E:58 client-id="1:0:24:d6:4a:3e:58" server=dhcp2 
     dhcp-option="" status=bound expires-after=6m9s last-seen=2m10s active-address=192.168.0.23 
     active-mac-address=00:24:D6:4A:3E:58 active-client-id="1:0:24:d6:4a:3e:58" active-server=dhcp2 
     host-name="Kamilla-VAIO" 

11 D address=192.168.0.41 mac-address=DC:2B:61:5A:59:D6 client-id="1:dc:2b:61:5a:59:d6" server=dhcp2 
     dhcp-option="" status=offered expires-after=27s last-seen=3s active-address=192.168.0.41 
     active-mac-address=DC:2B:61:5A:59:D6 active-client-id="1:dc:2b:61:5a:59:d6" active-server=dhcp2 
     host-name="iPhone" 

12 D address=192.168.0.40 mac-address=F0:DC:E2:65:E5:55 client-id="1:f0:dc:e2:65:e5:55" server=dhcp2 
     dhcp-option="" status=offered expires-after=26s last-seen=4s active-address=192.168.0.40 
     active-mac-address=F0:DC:E2:65:E5:55 active-client-id="1:f0:dc:e2:65:e5:55" active-server=dhcp2 
     host-name="Mikle"

And some hosts is not correct:

Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed 
 #    MAC-ADDRESS       ADDRESS         TO-ADDRESS      SERVER     IDLE-TIMEOUT
 3 HA 18:F4:6A:31:29:7A 192.168.0.13    192.168.0.13    hs-bridge1
 4 HA 18:F4:6A:13:43:E8 192.168.0.21    192.168.0.21    hs-bridge1
 5 HA DC:85:DE:22:B5:85 192.168.0.12    192.168.0.12    hs-bridge1
 6 DA 28:98:7B:33:86:CF 192.168.0.17    192.168.0.17    hs-bridge1
 7 D  7C:C3:A1:2A:9D:8C 192.168.0.3     192.168.0.3     hs-bridge1 10m         
 8 D  E8:06:88:7F:3B:3E 192.168.0.29    192.168.0.29    hs-bridge1 10m         
 9 H  A8:44:81:83:59:AA 192.168.0.6     192.168.0.6     hs-bridge1 10m         
10 D  28:98:7B:33:86:CF 192.168.0.8     192.168.0.8     hs-bridge1 10m         
11 D  5C:96:9D:45:47:E1 192.168.0.1     192.168.0.1     hs-bridge1 10m         
12 H  14:F4:2A:6E:82:7C 192.168.0.18    192.168.0.18    hs-bridge1 10m
14

Lease time is 10m:

ip dhcp-server print 
Flags: X - disabled, I - invalid 
 #   NAME     INTERFACE     RELAY           ADDRESS-POOL     LEASE-TIME ADD-ARP
 0 X dhcp1    ether2                        hs-pool-2        2m        
 1   dhcp2    bridge1                       hs-pool-2        10m
15

Now you say

Lease time is 10m:

but in your first response you said

Lease Time is 2 minutes.

If your information is incorrect, my response will be incorrect.

The only lease that appears strange is this one.

10 D address=192.168.0.23 mac-address=00:24:D6:4A:3E:58 client-id=“1:0:24:d6:4a:3e:58” server=dhcp2
dhcp-option=“” status=bound > expires-after=6m9s last-seen=2m10s > active-address=192.168.0.23
active-mac-address=00:24:D6:4A:3E:58 active-client-id=“1:0:24:d6:4a:3e:58” active-server=dhcp2
host-name=“Kamilla-VAIO”

What do you think is wrong with that hosts list. Looks ok to me.

Add: The other lease listed that the “expires-after” and “last-seen” do not equal 10 minutes are status=offered, and the times will total 30 seconds. That is the time remaining for that client to send a request for that offer.

16

Ok, it was 2 minutes and when you ask me, I`ve changed to 10 minutes.
Host list is good, I agree. This host list. But sometimes Address and To Address is not equal.

17

Host list is good, I agree. This host list. But sometimes Address and To Address is not equal.

Sometimes they are not, especially on a public access system. That has to do with the client and the last ip issued by dhcp to that client, and its expiration time. When the last lease the client received expires, the ips will match again. At least that is how it works here.

Add: Some client devices don’t update the assigned ip when connecting to another network. Those devices will not renew a lease until half the expiration time of the previous lease. That is why the address and to-address ips will be different for a while. If the client has a static ip assignment, and some of my clients do, they will never match.

18

ok. I understand it.

Now I am sitting right near Hotspot with my android phone:
My mac is A0:F4:50:14:7E:31

ip hotspot host print 
Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed 
 #    MAC-ADDRESS       ADDRESS         TO-ADDRESS      SERVER     IDLE-TIMEOUT
 0  P ;;;
      00:1C:10:66:ED:EA 10.0.36.42      10.0.36.42      hs-bridge1 10m         
 1  P ;;;
      00:0C:42:E1:82:A4 10.0.36.75      10.0.36.75      hs-bridge1 10m         
 2  P ;;;
      00:1C:10:66:E6:F1 10.0.36.41      10.0.36.41      hs-bridge1 10m         
 3 HA 08:ED:B9:6B:98:03 192.168.1.2     192.168.1.2     hs-bridge1
 4 HA 5C:0A:5B:94:FA:78 192.168.0.83    192.168.0.83    hs-bridge1
 5 H  E8:99:C4:4F:D9:BA 192.168.0.94    192.168.0.94    hs-bridge1 10m         
 6 H  1C:B0:94:34:DA:66 192.168.0.74    192.168.0.74    hs-bridge1 10m         
 7 DA 28:98:7B:33:86:CF 192.168.0.29    192.168.0.29    hs-bridge1
 8 DA A0:F4:50:14:7E:31 192.168.0.100   192.168.0.100   hs-bridge1
 9 HA BC:92:6B:1D:60:AE 192.168.0.95    192.168.0.95    hs-bridge1
10 D  F4:EC:38:A8:43:C8 10.0.36.90      192.168.0.11    hs-bridge1 10m         
11 D  28:98:7B:33:86:CF 192.168.0.99    192.168.0.99    hs-bridge1 10m         
12 DA A4:67:06:9C:39:C9 192.168.0.65    192.168.0.65    hs-bridge1
13 D  A4:67:06:9C:39:C9 192.168.0.102   192.168.0.102   hs-bridge1 10m         
14 H  A0:F4:50:14:7E:31 192.168.0.101   192.168.0.101   hs-bridge1 10m




6 D address=192.168.0.101 mac-address=A0:F4:50:14:7E:31 
     client-id="1:a0:f4:50:14:7e:31" server=dhcp2 dhcp-option="" status=bound 
     expires-after=9m57s last-seen=3s active-address=192.168.0.101 
     active-mac-address=A0:F4:50:14:7E:31 
     active-client-id="1:a0:f4:50:14:7e:31" active-server=dhcp2 
     host-name="android-fc94bfb609fe4547"

2 hosts records
lease is good, but switching bound/testing/offered … and when it starts browsing is not possible, pages not loads..
authorization brokes ..
But after second authorization everything good .. 1 host record, lease is not switching ..
So now I am trying to understand when it starts switching ..

19

2 hosts records
lease is good, but switching bound/testing/offered … and when it starts browsing is not possible, pages not loads..
authorization brokes ..
But after second authorization everything good .. 1 host record, lease is not switching ..
So now I am trying to understand when it starts switching ..

So am I. If the lease is switching bound/testing/offered, it isn’t good.
How do you login if the lease is cycling?
Does this cycling start when you login?
How often does it go through this cycle?
Can you see the expires-after value when status=bound?
How can you login a second time if it is cycling like that?

20

When bound status is active communication is possible and can login. If cycling is not fast.
Sometimes cycling stops without visible reasons..

3 statusses and everything is good, as i see ..

5 D address=192.168.0.4 mac-address=A0:F4:50:14:7E:31 client-id="1:a0:f4:50:14:7e:31" server=dhcp2 
     dhcp-option="" status=offered expires-after=30s last-seen=1s active-address=192.168.0.4 
     active-mac-address=A0:F4:50:14:7E:31 active-client-id="1:a0:f4:50:14:7e:31" active-server=dhcp2 
     host-name="android-fc94bfb609fe4547" 

6 D address=192.168.0.4 mac-address=A0:F4:50:14:7E:31 client-id="1:a0:f4:50:14:7e:31" server=dhcp2 
     dhcp-option="" status=testing expires-after=0s last-seen=0s active-address=192.168.0.4 
     active-mac-address=A0:F4:50:14:7E:31 active-client-id="1:a0:f4:50:14:7e:31" active-server=dhcp2 
     host-name="android-fc94bfb609fe4547" 

 D address=192.168.0.4 mac-address=A0:F4:50:14:7E:31 client-id="1:a0:f4:50:14:7e:31" server=dhcp2 
     dhcp-option="" status=bound expires-after=9m58s last-seen=2s active-address=192.168.0.4 
     active-mac-address=A0:F4:50:14:7E:31 active-client-id="1:a0:f4:50:14:7e:31" active-server=dhcp2 
     host-name="android-fc94bfb609fe4547"

But when there is 2 records in /ip hotspot hosts and addresses (Address and To Address) is not equal browsing is not possible at all.

Edit: I have no idea. I think low level dump is needed here. To analyze dhcp protocol…