zlacker

[return to "MacBook Pro Insomnia"]
◧
1. paulja+hb[view] [source] 2025-07-31 15:23:14
>>speckx+(OP)
This used to happen to my MacBook Pro, although it was a non Apple Silicon one. The issue was that I had changed the DHCP lease time on my router from the default to a really low value. I believe I had set it to 15 minutes. What I believe was happening was the MBP was waking up to renew its IP address every 15 minutes and by the time it went to sleep again, it was probably waking back up to repeat the process. Changing the value on the router back to its default completely fixed the battery drain issue on my MacBook Pro. I'd never have guessed the cause-effect except I made the change around the same time I purchased that new MacBook Pro and was paying more attention to any issues that might arise.
◧◩
2. ThePow+Tf[view] [source] 2025-07-31 15:50:16
>>paulja+hb
> I had changed the DHCP lease time on my router from the default to a really low value. I believe I had set it to 15 minutes.

What were you hoping to achieve by doing that?

◧◩◪
3. paulja+aD[view] [source] 2025-07-31 18:03:21
>>ThePow+Tf
I was trying to determine if a lease expired, if my router would immediately try to lease that same IP out to another machine on the network. It felt like it cached an expired lease mapping and would try to keep that old IP un-leased in case the original machine to which it was mapped came back online. I was just trying to better understand the behaviour.
◧◩◪◨
4. bigthy+we1[view] [source] 2025-07-31 21:57:11
>>paulja+aD
Did you want certain IPs to be fixed to certain devices or do you prefer they be randomly allocated?
◧◩◪◨⬒
5. paulja+Ei1[view] [source] 2025-07-31 22:30:52
>>bigthy+we1
Neither really, though my ISP's router would allow me to assign IPs by MAC address so they're effectively reserved to a device. The router's web UI displayed a list of devices. I wanted to see if devices would start dropping off this list as soon as the DHCP lease time expired. When they did drop off this list, I had thought they reappeared with the same IP without me explicitly using the reservation functionality. So how was this happening? I figured the web UI might not be showing the full picture of all the data about devices; that the router held records of formerly connected devices beyond the DHCP lease time for some unknown reason.
[go to top]