Hello,
On a constant basis we are always noticing assigned/deassigned IP addresses in the router logs. Is this an indication of any problems? If so would it have to do with access points or where would the issue come from.
Re: Assigned / deassigned log
You must be a much more generic,
and surely someone will help you.
and surely someone will help you.
Re: Assigned / deassigned log
What ROS version are you using? I had problems with some devices and dhcp in earlier versions prior to V6.5. Do the deassigned/assigned messages happen within a few seconds of each other?
Post a section of the log that has the symptoms you describe.
Also you might want to enable debug logging for dhcp.
Post a section of the log that has the symptoms you describe.
Also you might want to enable debug logging for dhcp.
Code: Select all
/system logging
add topics=dhcp,debug action=memory
Re: Assigned / deassigned log
We use a lot of different versions anywhere from 5.25 to 6.10. Also what do you mean by specific problems with some devices? I had always assumed that it was more or less related to an access point issue....What ROS version are you using? I had problems with some devices and dhcp in earlier versions prior to V6.5. Do the deassigned/assigned messages happen within a few seconds of each other?
Post a section of the log that has the symptoms you describe.
Also you might want to enable debug logging for dhcp.Code: Select all/system logging add topics=dhcp,debug action=memory
Re: Assigned / deassigned log
I can't help you if you don't answer my questions. Here they are:
1) Do you have problems with only some devices? Or is it all devices?
2) Do the deassigned/assigned messages happen within a few seconds of each other?
It might help to post a section of your log showing the problem.
1) Do you have problems with only some devices? Or is it all devices?
2) Do the deassigned/assigned messages happen within a few seconds of each other?
It might help to post a section of your log showing the problem.
Re: Assigned / deassigned log
I can't help you if you don't answer my questions. Here they are:
1) Do you have problems with only some devices? Or is it all devices?
2) Do the deassigned/assigned messages happen within a few seconds of each other?
It might help to post a section of your log showing the problem.
1. A lot of times its more or less mobile devices (I.E. androids/IOS) that tend to have this problem, but then again there is an excessive amount of assigned/deassigned happening quite rapidly.
2. Yes they do.
the version I am working with is 6.4 on this specific router.
You do not have the required permissions to view the files attached to this post.
Re: Assigned / deassigned log
I had the same problem. Like I said, the deassign/assign are just a few seconds apart. It looks like you have the same problem. I think this was fixed around v6.5, but I can't remember exactly. (edit: yes, it was fixed in v6.5)
If you want to see the problem:
Do the "print detail" now and then. The "expires-after" and "last-seen" values should total the lease time. The "last-seen" value should change at half the lease time, but if it is the same problem as mine, the "expires-after" time will not change every lease renewal, only when the "expires-after" value hits zero.
Upgrading was the answer for me.
If you want to see the problem:
Code: Select all
/ip dhcp-server lease
print detail
Upgrading was the answer for me.
Re: Assigned / deassigned log
It looks like it adds up properly. Although we are seeing this even from 6.5 and above.... I mean I will try the upgrade.I had the same problem. Like I said, the deassign/assign are just a few seconds apart. It looks like you have the same problem. I think this was fixed around v6.5, but I can't remember exactly. (edit: yes, it was fixed in v6.5)
If you want to see the problem:Do the "print detail" now and then. The "expires-after" and "last-seen" values should total the lease time. The "last-seen" value should change at half the lease time, but if it is the same problem as mine, the "expires-after" time will not change every lease renewal, only when the "expires-after" value hits zero.Code: Select all/ip dhcp-server lease print detail
Upgrading was the answer for me.
Re: Assigned / deassigned log
I added always broadcast check box and that seem to mitigate it as its not happening as much. What about the authoritative option? right now we have ours set to after 2s delay. Should that option be changed?
Re: Assigned / deassigned log
Did you check "/ip dhcp-server lease" to see what is happening with the "last-seen" and "expires-after" values? Those two values should add up to total the lease time. If you see any leases that the sum of those two values equals about half the lease time, then that may be the problem. That was mine. I let the MikroTik crew into my router to troubleshoot the problem, and the fix in v6.5 is the result. Maybe they didn't get every bug out of it.
Re: Assigned / deassigned log
Yes the time added up correctly. I wouldn't be surprised if its not fully fixed. At any rate should the authoritative 2s delay be left alone?Did you check "/ip dhcp-server lease" to see what is happening with the "last-seen" and "expires-after" values? Those two values should add up to total the lease time. If you see any leases that the sum of those two values equals about half the lease time, then that may be the problem. That was mine. I let the MikroTik crew into my router to troubleshoot the problem, and the fix in v6.5 is the result. Maybe they didn't get every bug out of it.
-
-
moltenlogic
just joined
- Posts: 1
- Joined:
Re: Assigned / deassigned log
I was seeing this on 6.32.2 in a building with 9 Ubiquiti UniFi access points in a dense configuration. Only some clients were affected. I captured packets on both router and client to troubleshoot the issue to see if it was a problem with packets getting from place to place.
It turns out, this could be perfectly normal! In my case it was simply some clients roaming between access points and requesting new IP leases. (I spent some time troubleshooting this, so I'll break it down to help others and boost Google search results for the next person...)
DETAILS
As you know a basic DHCP conversation goes like this:
1- Client sends a "discover" to ask for an IP
2- Server responds to "offer" an available IP
3- Client officially does a "request" for the IP
4- Server responds with "ack" to complete the transaction and record the lease
When switching from one access point to another, especially with the same SSID, some clients will start at step 3 and send a "request" to make sure their IP address is still valid. And the router will simply respond with an "ack".
BUT some clients will start over with "discover" asking for a totally new IP lease. When this happens, RouterOS realizes there is already an IP lease for this client, but removes it because it is now outdated. Hence the "deassigned" log message. The router then "offers" a new IP lease (probably for the same IP address) and it gets requested and ack'd. Hence the "assigned" log entry for the same IP/MAC almost immediately after the "deassigned" entry. It's simply dropping the old lease and creating a new lease for the same IP.
By the way - I also saw occasional "offering lease without success" messages. My packet captures at both ends confirmed the broadcast packets were getting to everyone else. After comparing to Access Point logs, I found these clients were on a fringe connection, probably outside the building, connecting just long enough to "discover" an IP but out of range before it could be requested. If this happens repeatedly, the RouterOS seems to flag your attention. If it happens consistently it could be a firewall or other blocking issue, but in my case it was relatively rare and just indicated a poorly connected client.
Hope this helps someone else because I was really concerned for awhile!
It turns out, this could be perfectly normal! In my case it was simply some clients roaming between access points and requesting new IP leases. (I spent some time troubleshooting this, so I'll break it down to help others and boost Google search results for the next person...)
DETAILS
As you know a basic DHCP conversation goes like this:
1- Client sends a "discover" to ask for an IP
2- Server responds to "offer" an available IP
3- Client officially does a "request" for the IP
4- Server responds with "ack" to complete the transaction and record the lease
When switching from one access point to another, especially with the same SSID, some clients will start at step 3 and send a "request" to make sure their IP address is still valid. And the router will simply respond with an "ack".
BUT some clients will start over with "discover" asking for a totally new IP lease. When this happens, RouterOS realizes there is already an IP lease for this client, but removes it because it is now outdated. Hence the "deassigned" log message. The router then "offers" a new IP lease (probably for the same IP address) and it gets requested and ack'd. Hence the "assigned" log entry for the same IP/MAC almost immediately after the "deassigned" entry. It's simply dropping the old lease and creating a new lease for the same IP.
By the way - I also saw occasional "offering lease without success" messages. My packet captures at both ends confirmed the broadcast packets were getting to everyone else. After comparing to Access Point logs, I found these clients were on a fringe connection, probably outside the building, connecting just long enough to "discover" an IP but out of range before it could be requested. If this happens repeatedly, the RouterOS seems to flag your attention. If it happens consistently it could be a firewall or other blocking issue, but in my case it was relatively rare and just indicated a poorly connected client.
Hope this helps someone else because I was really concerned for awhile!
Re: Assigned / deassigned log
Hello,1. A lot of times its more or less mobile devices (I.E. androids/IOS) that tend to have this problem, but then again there is an excessive amount of assigned/deassigned happening quite rapidly.I can't help you if you don't answer my questions. Here they are:
1) Do you have problems with only some devices? Or is it all devices?
2) Do the deassigned/assigned messages happen within a few seconds of each other?
It might help to post a section of your log showing the problem.
2. Yes they do.
ROS 7.13.3
Router/CAPSMAN + 2 APs (hap ax2 and hap ax3). They are connected by a managed DLINK switch. No VLANS.
When moving from one AP to another, android phones often loose connectivity. They show "Connected without internet", and disconnects from wifi. I do not see the right IP address at this time on the phones. I think, it disconnects because it does not get the IP address, so it switches to mobile data.
The second "roamed" line says that the phone changes the AP.
In the DHCP window the 192.168.1.111 address is shown as "conflict" with MAC address full of zeroes (00:00:00:00:00:00).
Code: Select all
19:17:59 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:07 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:08 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:15 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:15 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:24 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:24 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:27 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:27 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:35 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:35 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:42 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:42 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:46 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:18:46 dhcp,info additional assigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:35:36 wireless,info 64:B5:F2:D2:6B:57@cap-wifi3 roamed to 64:B5:F2:D2:6B:57@cap-wifi5, signal strength -82
19:37:38 wireless,info 64:B5:F2:D2:6B:57@cap-wifi5 roamed to 64:B5:F2:D2:6B:57@cap-wifi2, signal strength -65
19:37:47 dhcp,info additional deassigned 192.168.1.111 for 64:B5:F2:D2:6B:57 S23
19:37:47 dhcp,warning Detected conflict by ARP response for 192.168.1.111 from 64:B5:F2:D2:6B:57
19:37:54 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:37:57 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:37:57 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:01 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:01 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:06 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:06 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:09 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:09 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:12 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:12 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:16 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:16 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:19 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:19 dhcp,info additional assigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
19:38:23 dhcp,info additional deassigned 192.168.1.110 for 64:B5:F2:D2:6B:57 S23
Re: Assigned / deassigned log
Who knows .... ?
- enable dhcp,debug to see more?
- no internet access after getting the IP address, some clients then drop the wifi connection, then dhcp deassigns ???
- DHCP D.O.R.A sequence is stuck at O=offered. The (ping) check fails after the 2sec aurhorative delay ??? DHCP lease Status does not go to "bound" ??? DHCP server drops lease.
- enable dhcp,debug to see more?
- no internet access after getting the IP address, some clients then drop the wifi connection, then dhcp deassigns ???
- DHCP D.O.R.A sequence is stuck at O=offered. The (ping) check fails after the 2sec aurhorative delay ??? DHCP lease Status does not go to "bound" ??? DHCP server drops lease.
Re: Assigned / deassigned log
How to enable dhcp debug? Where to look?Who knows .... ?
- enable dhcp,debug to see more?
- no internet access after getting the IP address, some clients then drop the wifi connection, then dhcp deassigns ???
- DHCP D.O.R.A sequence is stuck at O=offered. The (ping) check fails after the 2sec aurhorative delay ??? DHCP lease Status does not go to "bound" ??? DHCP server drops lease.
Yes, it looks like android clients do some tests and don't like the connection from different access point. It all started with ISP's DHCP, so i enabled Mikrotik's DHCP with 2 sec. 2 sec authoritative delay is ON because of ISP router's DHCP. I use non-overlapping pool to exclude ISP's router-related problems. Everything is plugged into DLINK managed switch (different ports). I have already reduced ARP aging timeout on the switch from 300 to 50 seconds, but i do not see much difference...'
To debug the sequence, do i need port-mirrored wireshark on switch, or mikrotik can provide an alternative?
Maybe i need to check the external DLINK switch settings? Which ones?
Thanks
Re: Assigned / deassigned log
How to enable dhcp debug? Where to look?
In system / logging add a double topic "dhcp" and "debug" , output will be in the log.
"packet" is also possible to see even more, or use "!packet" to suppress the large packet based output.
Having more than one DHCP server on a network is mostly a problem. Non-overlapping pool has not been a solution for me with MT, when setting up redundant DHCP servers: they NACK each others leases, and clients flap between the DHCP servers. (Other implementations have a "ignore range" setting or something to avoid NACKing, I presume.)so i enabled Mikrotik's DHCP with 2 sec. 2 sec authoritative delay is ON because of ISP router's DHCP. I use non-overlapping pool to exclude ISP's router-related problems.
The MT Tools 'Packet Sniffer 'can help you. If you give it a file name, it will save the captured packets in that file. File which can be downloaded, and the packets analysed with Wireshark.To debug the sequence, do i need port-mirrored wireshark on switch, or mikrotik can provide an alternative?
Re: Assigned / deassigned log
Hello,In system / logging add a double topic "dhcp" and "debug" , output will be in the log.
"packet" is also possible to see even more, or use "!packet" to suppress the large packet based output.
Having more than one DHCP server on a network is mostly a problem. Non-overlapping pool has not been a solution for me with MT, when setting up redundant DHCP servers: they NACK each others leases, and clients flap between the DHCP servers. (Other implementations have a "ignore range" setting or something to avoid NACKing, I presume.)
I started having these connectivity problems even before i activated the second DHCP server. So, i have activated it for another pool of addresses. It helps a little, but not much. The status shows as "bound", but the smartphone does not show wifi, it uses mobile data.
Here is the debug log:
Code: Select all
15:31:52 dhcp,debug lease found, bound, offer
15:31:52 dhcp,info defconf deassigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:31:52 dhcp,debug defconf sending offer with id 3095779895 to 255.255.255.255
15:31:52 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:52 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:52 dhcp,debug,packet siaddr = 192.168.1.4
15:31:52 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:52 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:52 dhcp,debug,packet Router = 192.168.1.1
15:31:52 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:52 dhcp,debug,packet Address-Time = 600
15:31:52 dhcp,debug,packet Msg-Type = offer
15:31:52 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:52 dhcp,debug defconf received request id 3095779895 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:52 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:52 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:52 dhcp,debug,packet Host-Name = "S23"
15:31:52 dhcp,debug,packet Address-Request = 192.168.1.110
15:31:52 dhcp,debug,packet Msg-Type = request
15:31:52 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:52 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:52 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:52 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:52 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:52 dhcp,debug lease offered, addressed to me
15:31:52 dhcp,info defconf assigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:31:52 dhcp,debug defconf sending ack with id 3095779895 to 255.255.255.255
15:31:52 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:52 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:52 dhcp,debug,packet siaddr = 192.168.1.4
15:31:52 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:52 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:52 dhcp,debug,packet Router = 192.168.1.1
15:31:52 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:52 dhcp,debug,packet Address-Time = 600
15:31:52 dhcp,debug,packet Msg-Type = ack
15:31:52 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:56 dhcp,debug defconf received request id 3770334981 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Host-Name = "S23"
15:31:56 dhcp,debug,packet Address-Request = 192.168.1.110
15:31:56 dhcp,debug,packet Msg-Type = request
15:31:56 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:56 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:56 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:56 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:56 dhcp,debug lease bound, init-reboot, extending
15:31:56 dhcp,debug defconf sending ack with id 3770334981 to 255.255.255.255
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:56 dhcp,debug,packet siaddr = 192.168.1.4
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:56 dhcp,debug,packet Router = 192.168.1.1
15:31:56 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:56 dhcp,debug,packet Address-Time = 600
15:31:56 dhcp,debug,packet Msg-Type = ack
15:31:56 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:56 dhcp,debug defconf received discover id 392814734 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Host-Name = "S23"
15:31:56 dhcp,debug,packet Msg-Type = discover
15:31:56 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:56 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:56 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:56 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:56 dhcp,debug,packet Unknown(80) =
15:31:56 dhcp,debug lease found, bound, offer
15:31:56 dhcp,info defconf deassigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:31:56 dhcp,debug defconf sending offer with id 392814734 to 255.255.255.255
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:56 dhcp,debug,packet siaddr = 192.168.1.4
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:56 dhcp,debug,packet Router = 192.168.1.1
15:31:56 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:56 dhcp,debug,packet Address-Time = 600
15:31:56 dhcp,debug,packet Msg-Type = offer
15:31:56 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:56 dhcp,debug defconf received request id 392814734 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Host-Name = "S23"
15:31:56 dhcp,debug,packet Address-Request = 192.168.1.110
15:31:56 dhcp,debug,packet Msg-Type = request
15:31:56 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:56 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:56 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:56 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:56 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:56 dhcp,debug lease offered, addressed to me
15:31:56 dhcp,info defconf assigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:31:56 dhcp,debug defconf sending ack with id 392814734 to 255.255.255.255
15:31:56 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:56 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:56 dhcp,debug,packet siaddr = 192.168.1.4
15:31:56 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:56 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:56 dhcp,debug,packet Router = 192.168.1.1
15:31:56 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:56 dhcp,debug,packet Address-Time = 600
15:31:56 dhcp,debug,packet Msg-Type = ack
15:31:56 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:59 dhcp,debug defconf received request id 1712315437 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:59 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:59 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:59 dhcp,debug,packet Host-Name = "S23"
15:31:59 dhcp,debug,packet Address-Request = 192.168.1.110
15:31:59 dhcp,debug,packet Msg-Type = request
15:31:59 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:59 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:59 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:59 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:59 dhcp,debug lease bound, init-reboot, extending
15:31:59 dhcp,debug defconf sending ack with id 1712315437 to 255.255.255.255
15:31:59 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:59 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:59 dhcp,debug,packet siaddr = 192.168.1.4
15:31:59 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:59 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:59 dhcp,debug,packet Router = 192.168.1.1
15:31:59 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:59 dhcp,debug,packet Address-Time = 600
15:31:59 dhcp,debug,packet Msg-Type = ack
15:31:59 dhcp,debug,packet Server-Id = 192.168.1.4
15:31:59 dhcp,debug defconf received discover id 3828384008 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:31:59 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:59 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:59 dhcp,debug,packet Host-Name = "S23"
15:31:59 dhcp,debug,packet Msg-Type = discover
15:31:59 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:31:59 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:31:59 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:31:59 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:31:59 dhcp,debug,packet Unknown(80) =
15:31:59 dhcp,debug lease found, bound, offer
15:31:59 dhcp,info defconf deassigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:31:59 dhcp,debug defconf sending offer with id 3828384008 to 255.255.255.255
15:31:59 dhcp,debug,packet ciaddr = 0.0.0.0
15:31:59 dhcp,debug,packet yiaddr = 192.168.1.110
15:31:59 dhcp,debug,packet siaddr = 192.168.1.4
15:31:59 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:31:59 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:31:59 dhcp,debug,packet Router = 192.168.1.1
15:31:59 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:31:59 dhcp,debug,packet Address-Time = 600
15:31:59 dhcp,debug,packet Msg-Type = offer
15:31:59 dhcp,debug,packet Server-Id = 192.168.1.4
15:32:00 dhcp,debug defconf received request id 3828384008 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
15:32:00 dhcp,debug,packet ciaddr = 0.0.0.0
15:32:00 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:32:00 dhcp,debug,packet Host-Name = "S23"
15:32:00 dhcp,debug,packet Address-Request = 192.168.1.110
15:32:00 dhcp,debug,packet Msg-Type = request
15:32:00 dhcp,debug,packet Server-Id = 192.168.1.4
15:32:00 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,A
ddress-Time,Renewal-Time,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:32:00 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:32:00 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:32:00 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:32:00 dhcp,debug lease offered, addressed to me
15:32:00 dhcp,info defconf assigned 192.168.1.110 for 64:B5:F2:D2:1B:17 S23
15:32:00 dhcp,debug defconf sending ack with id 3828384008 to 255.255.255.255
15:32:00 dhcp,debug,packet ciaddr = 0.0.0.0
15:32:00 dhcp,debug,packet yiaddr = 192.168.1.110
15:32:00 dhcp,debug,packet siaddr = 192.168.1.4
15:32:00 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:32:00 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:32:00 dhcp,debug,packet Router = 192.168.1.1
15:32:00 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:32:00 dhcp,debug,packet Address-Time = 600
15:32:00 dhcp,debug,packet Msg-Type = ack
15:32:00 dhcp,debug,packet Server-Id = 192.168.1.4
Code: Select all
15:38:49 dhcp,debug defconf received request id 413612910 from 192.168.1.110 '1:64:b5:f2:d2:1B:17'
15:38:49 dhcp,debug,packet ciaddr = 192.168.1.110
15:38:49 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:38:49 dhcp,debug,packet Host-Name = "S23"
15:38:49 dhcp,debug,packet Msg-Type = request
15:38:49 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time
,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:38:49 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:38:49 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:38:49 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:38:49 dhcp,debug lease bound, extending
15:38:49 dhcp,debug defconf sending ack with id 413612910 to 255.255.255.255
15:38:49 dhcp,debug,packet ciaddr = 192.168.1.110
15:38:49 dhcp,debug,packet yiaddr = 192.168.1.110
15:38:49 dhcp,debug,packet siaddr = 192.168.1.4
15:38:49 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:38:49 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:38:49 dhcp,debug,packet Router = 192.168.1.1
15:38:49 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:38:49 dhcp,debug,packet Address-Time = 600
15:38:49 dhcp,debug,packet Msg-Type = ack
15:38:49 dhcp,debug,packet Server-Id = 192.168.1.4
15:43:49 dhcp,debug defconf received request id 2369360054 from 192.168.1.110 '1:64:b5:f2:d2:1B:17'
15:43:49 dhcp,debug,packet ciaddr = 192.168.1.110
15:43:49 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:43:49 dhcp,debug,packet Host-Name = "S23"
15:43:49 dhcp,debug,packet Msg-Type = request
15:43:49 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time
,Rebinding-Time,Vendor-Specific,Captive-Portal,IPv6-Only Preferred
15:43:49 dhcp,debug,packet Max-DHCP-Message-Size = 1500
15:43:49 dhcp,debug,packet Class-Id = "android-dhcp-14"
15:43:49 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
15:43:49 dhcp,debug lease bound, extending
15:43:49 dhcp,debug defconf sending ack with id 2369360054 to 255.255.255.255
15:43:49 dhcp,debug,packet ciaddr = 192.168.1.110
15:43:49 dhcp,debug,packet yiaddr = 192.168.1.110
15:43:49 dhcp,debug,packet siaddr = 192.168.1.4
15:43:49 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
15:43:49 dhcp,debug,packet Subnet-Mask = 255.255.255.0
15:43:49 dhcp,debug,packet Router = 192.168.1.1
15:43:49 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
15:43:49 dhcp,debug,packet Address-Time = 600
15:43:49 dhcp,debug,packet Msg-Type = ack
15:43:49 dhcp,debug,packet Server-Id = 192.168.1.4
Re: Assigned / deassigned log
Somebody with more DHCP experience might help here.
But I do see Discover-Offer-Request-Ack sequence as expected, but there is instantly a new discover. As if the Ack was not received or accepted by the client.
In the second part the client has taken and uses the IP lease address. (ciaddr) https://techhub.hpe.com/eginfolib/netwo ... 823386.htm
The ACK is sent to 255.255.255.255 , and if broadcast/multicast is used in wifi, this is then a different transmission mode from unicast.
Unicasts must be acknowledged by the receiving side , or will be retried by wifi untill it succeeds (wifi will lower encoding en interface rates due to fails, to make it work)
Broadcast/multicast is only sent once, at the "interface basic rate". It must succeed with the first transmission, therefor the use of the mostly low "basic" rate.
If there is a disturbed wifi connection, this multicast/broadcast will fail. Unicast could survive with numerous attempts.
(In the legacy/old WLAN driver , we can set how many retransmits are used, and see how many failures are detected. Default is 7 transmits before interface steps down the rate, and then when arrived at the lowest rate, 3 seconds retries, every 0.1 seconds. Failing even this will disconnect the client with "extensive data loss".)
But I do see Discover-Offer-Request-Ack sequence as expected, but there is instantly a new discover. As if the Ack was not received or accepted by the client.
In the second part the client has taken and uses the IP lease address. (ciaddr) https://techhub.hpe.com/eginfolib/netwo ... 823386.htm
The ACK is sent to 255.255.255.255 , and if broadcast/multicast is used in wifi, this is then a different transmission mode from unicast.
Unicasts must be acknowledged by the receiving side , or will be retried by wifi untill it succeeds (wifi will lower encoding en interface rates due to fails, to make it work)
Broadcast/multicast is only sent once, at the "interface basic rate". It must succeed with the first transmission, therefor the use of the mostly low "basic" rate.
If there is a disturbed wifi connection, this multicast/broadcast will fail. Unicast could survive with numerous attempts.
(In the legacy/old WLAN driver , we can set how many retransmits are used, and see how many failures are detected. Default is 7 transmits before interface steps down the rate, and then when arrived at the lowest rate, 3 seconds retries, every 0.1 seconds. Failing even this will disconnect the client with "extensive data loss".)
Re: Assigned / deassigned log
WiFi is not too disturbed here, at least the 5GHz band is free.Somebody with more DHCP experience might help here.
But I do see Discover-Offer-Request-Ack sequence as expected, but there is instantly a new discover. As if the Ack was not received or accepted by the client.
In the second part the client has taken and uses the IP lease address. (ciaddr) https://techhub.hpe.com/eginfolib/netwo ... 823386.htm
The ACK is sent to 255.255.255.255 , and if broadcast/multicast is used in wifi, this is then a different transmission mode from unicast.
Unicasts must be acknowledged by the receiving side , or will be retried by wifi untill it succeeds (wifi will lower encoding en interface rates due to fails, to make it work)
Broadcast/multicast is only sent once, at the "interface basic rate". It must succeed with the first transmission, therefor the use of the mostly low "basic" rate.
If there is a disturbed wifi connection, this multicast/broadcast will fail. Unicast could survive with numerous attempts.
(In the legacy/old WLAN driver , we can set how many retransmits are used, and see how many failures are detected. Default is 7 transmits before interface steps down the rate, and then when arrived at the lowest rate, 3 seconds retries, every 0.1 seconds. Failing even this will disconnect the client with "extensive data loss".)
Maybe the switch in between does not update its ARP/MAC table as soon as the client appears on the other port? It is an old DLINK DGS-3000-10T. Or, maybe i miss some configuration parameter for this switch...
When i roam downstairs, the phone switches OK, but when i roam back upstairs, it does not see the internet.
Recently i have seen a conflict - that may be when the phone asks for other DHCP server's address, but this is relatively rare and i don't think that it is related to this whole assigned/deassigned thing.
Code: Select all
19:17:22 dhcp,debug defconf received discover id 1281359796 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:22 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:22 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:22 dhcp,debug,packet Host-Name = "S23"
19:17:22 dhcp,debug,packet Msg-Type = discover
19:17:22 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:22 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:22 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:22 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:22 dhcp,debug,packet Unknown(80) =
19:17:22 dhcp,debug lease found, bound, offer
19:17:22 dhcp,info defconf deassigned 192.168.1.102 for 64:B5:F2:D2:1B:17 S23
19:17:22 dhcp,debug defconf sending offer with id 1281359796 to 255.255.255.255
19:17:22 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:22 dhcp,debug,packet yiaddr = 192.168.1.102
19:17:22 dhcp,debug,packet siaddr = 192.168.1.4
19:17:22 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:22 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:22 dhcp,debug,packet Router = 192.168.1.1
19:17:22 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:22 dhcp,debug,packet Address-Time = 1200
19:17:22 dhcp,debug,packet Msg-Type = offer
19:17:22 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:22 dhcp,debug defconf received request id 1281359796 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:22 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:22 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:22 dhcp,debug,packet Host-Name = "S23"
19:17:22 dhcp,debug,packet Address-Request = 192.168.1.102
19:17:22 dhcp,debug,packet Msg-Type = request
19:17:22 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:22 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:22 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:22 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:22 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:22 dhcp,debug lease offered, addressed to me
19:17:22 dhcp,info defconf assigned 192.168.1.102 for 64:B5:F2:D2:1B:17 S23
19:17:22 dhcp,debug defconf sending ack with id 1281359796 to 255.255.255.255
19:17:22 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:22 dhcp,debug,packet yiaddr = 192.168.1.102
19:17:22 dhcp,debug,packet siaddr = 192.168.1.4
19:17:22 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:22 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:22 dhcp,debug,packet Router = 192.168.1.1
19:17:22 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:22 dhcp,debug,packet Address-Time = 1200
19:17:22 dhcp,debug,packet Msg-Type = ack
19:17:22 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:31 wireless,info 64:B5:F2:D2:1B:17@cap-wif7 disconnected, connection lost, signal strength -62
19:17:31 wireless,info 64:B5:F2:D2:1B:17@cap-wifi1 connected, signal strength -64
19:17:31 dhcp,debug defconf received request id 1792477009 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:31 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:31 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:31 dhcp,debug,packet Host-Name = "S23"
19:17:31 dhcp,debug,packet Address-Request = 192.168.1.184
19:17:31 dhcp,debug,packet Msg-Type = request
19:17:31 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:31 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:31 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:31 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:31 dhcp,debug lease bound, init-reboot, extending, wrong ip requested 192.168.1.184
19:17:31 dhcp,debug defconf sending nak with id 1792477009 to 255.255.255.255
19:17:31 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:31 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:31 dhcp,debug,packet Msg-Type = nak
19:17:31 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:31 dhcp,info defconf deassigned 192.168.1.102 for 64:B5:F2:D2:1B:17 S23
19:17:31 dhcp,debug defconf received discover id 1857094831 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:31 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:31 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:31 dhcp,debug,packet Host-Name = "S23"
19:17:31 dhcp,debug,packet Msg-Type = discover
19:17:31 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:31 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:31 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:31 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:31 dhcp,debug,packet Unknown(80) =
19:17:31 dhcp,debug lease not found, new lease, acquire
19:17:31 dhcp,debug ping 192.168.1.102
19:17:31 dhcp,warning Detected conflict by ARP response for 192.168.1.102 from 64:B5:F2:D2:1B:17
19:17:31 dhcp,debug ping done 192.168.1.102
19:17:32 dhcp,debug defconf received discover id 1857094831 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:32 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:32 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:32 dhcp,debug,packet Host-Name = "S23"
19:17:32 dhcp,debug,packet Msg-Type = discover
19:17:32 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:32 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:32 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:32 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:32 dhcp,debug,packet Unknown(80) =
19:17:32 dhcp,debug lease not found, new lease, acquire
19:17:32 dhcp,debug ping 192.168.1.101
19:17:33 dhcp,debug ping done 192.168.1.101
19:17:33 dhcp,debug defconf sending offer with id 1857094831 to 192.168.1.101
19:17:33 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:33 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:33 dhcp,debug,packet siaddr = 192.168.1.4
19:17:33 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:33 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:33 dhcp,debug,packet Router = 192.168.1.1
19:17:33 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:33 dhcp,debug,packet Address-Time = 1200
19:17:33 dhcp,debug,packet Msg-Type = offer
19:17:33 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:34 dhcp,debug defconf received discover id 1857094831 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:34 dhcp,debug,packet secs = 2
19:17:34 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:34 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:34 dhcp,debug,packet Host-Name = "S23"
19:17:34 dhcp,debug,packet Msg-Type = discover
19:17:34 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:34 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:34 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:34 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:34 dhcp,debug,packet Unknown(80) =
19:17:34 dhcp,debug lease found, offered, offer
19:17:34 dhcp,debug defconf sending offer with id 1857094831 to 192.168.1.101
19:17:34 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:34 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:34 dhcp,debug,packet siaddr = 192.168.1.4
19:17:34 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:34 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:34 dhcp,debug,packet Router = 192.168.1.1
19:17:34 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:34 dhcp,debug,packet Address-Time = 1200
19:17:34 dhcp,debug,packet Msg-Type = offer
19:17:34 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:38 dhcp,debug defconf received discover id 1857094831 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:38 dhcp,debug,packet secs = 6
19:17:38 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:38 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:38 dhcp,debug,packet Host-Name = "S23"
19:17:38 dhcp,debug,packet Msg-Type = discover
19:17:38 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:38 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:38 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:38 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:38 dhcp,debug lease found, offered, offer
19:17:38 dhcp,debug 3 offers in a row => forcing broadcast
19:17:38 dhcp,debug defconf sending offer with id 1857094831 to 255.255.255.255
19:17:38 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:38 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:38 dhcp,debug,packet siaddr = 192.168.1.4
19:17:38 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:38 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:38 dhcp,debug,packet Router = 192.168.1.1
19:17:38 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:38 dhcp,debug,packet Address-Time = 1200
19:17:38 dhcp,debug,packet Msg-Type = offer
19:17:38 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:38 dhcp,debug defconf received request id 1857094831 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:38 dhcp,debug,packet secs = 6
19:17:38 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:38 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:38 dhcp,debug,packet Host-Name = "S23"
19:17:38 dhcp,debug,packet Address-Request = 192.168.1.101
19:17:38 dhcp,debug,packet Msg-Type = request
19:17:38 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:38 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:38 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:38 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:38 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:38 dhcp,debug lease offered, addressed to me
19:17:38 dhcp,info defconf assigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:17:38 dhcp,debug defconf sending ack with id 1857094831 to 255.255.255.255
19:17:38 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:38 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:38 dhcp,debug,packet siaddr = 192.168.1.4
19:17:38 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:38 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:38 dhcp,debug,packet Router = 192.168.1.1
19:17:38 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:38 dhcp,debug,packet Address-Time = 1200
19:17:38 dhcp,debug,packet Msg-Type = ack
19:17:38 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:42 dhcp,debug defconf received request id 312568575 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Host-Name = "S23"
19:17:42 dhcp,debug,packet Address-Request = 192.168.1.101
19:17:42 dhcp,debug,packet Msg-Type = request
19:17:42 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:42 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:42 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:42 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:42 dhcp,debug lease bound, init-reboot, extending
19:17:42 dhcp,debug defconf sending ack with id 312568575 to 255.255.255.255
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:42 dhcp,debug,packet siaddr = 192.168.1.4
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:42 dhcp,debug,packet Router = 192.168.1.1
19:17:42 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:42 dhcp,debug,packet Address-Time = 1200
19:17:42 dhcp,debug,packet Msg-Type = ack
19:17:42 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:42 dhcp,debug defconf received discover id 3091516165 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Host-Name = "S23"
19:17:42 dhcp,debug,packet Msg-Type = discover
19:17:42 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:42 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:42 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:42 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:42 dhcp,debug,packet Unknown(80) =
19:17:42 dhcp,debug lease found, bound, offer
19:17:42 dhcp,info defconf deassigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:17:42 dhcp,debug defconf sending offer with id 3091516165 to 255.255.255.255
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:42 dhcp,debug,packet siaddr = 192.168.1.4
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:42 dhcp,debug,packet Router = 192.168.1.1
19:17:42 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:42 dhcp,debug,packet Address-Time = 1200
19:17:42 dhcp,debug,packet Msg-Type = offer
19:17:42 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:42 dhcp,debug defconf received request id 3091516165 from 0.0.0.0 '1:64:b5:f2:d2:1B:17'
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Host-Name = "S23"
19:17:42 dhcp,debug,packet Address-Request = 192.168.1.101
19:17:42 dhcp,debug,packet Msg-Type = request
19:17:42 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:42 dhcp,debug,packet Parameter-List = Subnet-Mask,Router,Domain-Server,Domain-Name,Interface-MTU,Broadcast-Address,Address-Time,Renewal-Time,Rebinding-Time,
Vendor-Specific,Captive-Portal,IPv6-Only Preferred
19:17:42 dhcp,debug,packet Max-DHCP-Message-Size = 1500
19:17:42 dhcp,debug,packet Class-Id = "android-dhcp-14"
19:17:42 dhcp,debug,packet Client-Id = 01-64-B5-F2-D2-1B-17
19:17:42 dhcp,debug lease offered, addressed to me
19:17:42 dhcp,info defconf assigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:17:42 dhcp,debug defconf sending ack with id 3091516165 to 255.255.255.255
19:17:42 dhcp,debug,packet ciaddr = 0.0.0.0
19:17:42 dhcp,debug,packet yiaddr = 192.168.1.101
19:17:42 dhcp,debug,packet siaddr = 192.168.1.4
19:17:42 dhcp,debug,packet chaddr = 64:B5:F2:D2:1B:17
19:17:42 dhcp,debug,packet Subnet-Mask = 255.255.255.0
19:17:42 dhcp,debug,packet Router = 192.168.1.1
19:17:42 dhcp,debug,packet Domain-Server = 192.168.1.32,192.168.1.33,192.168.1.1
19:17:42 dhcp,debug,packet Address-Time = 1200
19:17:42 dhcp,debug,packet Msg-Type = ack
19:17:42 dhcp,debug,packet Server-Id = 192.168.1.4
19:17:53 system,info log rule changed by winbox-3.40/tcp-msg(winbox):dimadm@192.168.1.20 (/system logging set "" action=memory disabled=yes prefix="" topics=dhcp,debug)
19:17:54 dhcp,info defconf deassigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:17:54 dhcp,info defconf assigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:17:57 wireless,info 64:B5:F2:D2:1B:17@cap-wifi1 disconnected, connection lost, signal strength -65
19:18:01 wireless,info 64:B5:F2:D2:1B:17@cap-wif7 connected, signal strength -66
19:18:01 dhcp,info defconf deassigned 192.168.1.101 for 64:B5:F2:D2:1B:17 S23
19:18:01 dhcp,warning Detected conflict by ARP response for 192.168.1.101 from 64:B5:F2:D2:1B:17
19:18:09 dhcp,info defconf assigned 192.168.1.129 for 64:B5:F2:D2:1B:17 S23
19:18:12 dhcp,info defconf deassigned 192.168.1.129 for 64:B5:F2:D2:1B:17 S23
Re: Assigned / deassigned log
I have checked with the switch, it updates its MAC address table and shows the correct port where the phone goes. The MAC address follows the switch port correctly, the switch web interface shows me how the ports change when i search for the MAC address in question.
This is strange. When phone roams from HAP AX2 to HAP AX3 - no problem. When it roams back from AX3 to AX2 - it does not see itself connected anymore. Another chineese phone shows the attempts in real time:
It shows the acquired IPv4 address, link-local IPv6, but no global IPv6 address acquired via SLAAC. In 1-2 seconds it drops them all and repeats the attempt. I see in the logs the same assigned/deassigned messages until it finally acquires all the addresses.
Is it necessary to obtain an IPv6 address for android phone in order to be satisfied with the DHCP lease offered?
Maybe i need to check some config in AX2?
BTW, the router/controller acts as a transparent firewall between the ISP router and my LAN (flat L2 LAN, no internal routing). Broadcasts and multicasts are allowed, intra-LAN communications are enabled.
This is strange. When phone roams from HAP AX2 to HAP AX3 - no problem. When it roams back from AX3 to AX2 - it does not see itself connected anymore. Another chineese phone shows the attempts in real time:
It shows the acquired IPv4 address, link-local IPv6, but no global IPv6 address acquired via SLAAC. In 1-2 seconds it drops them all and repeats the attempt. I see in the logs the same assigned/deassigned messages until it finally acquires all the addresses.
Is it necessary to obtain an IPv6 address for android phone in order to be satisfied with the DHCP lease offered?
Maybe i need to check some config in AX2?
BTW, the router/controller acts as a transparent firewall between the ISP router and my LAN (flat L2 LAN, no internal routing). Broadcasts and multicasts are allowed, intra-LAN communications are enabled.
Re: Assigned / deassigned log
I had 2 bridges configured on this router. The default switch was dealing with what was not directly connected to the transparent firewall bridge. I have moved all the functions to the default bridge.Somebody with more DHCP experience might help here.
I have also enabled RSTP.
And it looks like working now. I do not see these Assigned / deassigned.
Some chinese phones still hesitate sometimes, but i will look into this later.