Comment by tomxor
4 years ago
> And I learnt that even when it is not used (not sure it the lid was closed) a macbook can cause significant interference to the wifi for all other nearby devices.
My partner has an older MBP, I noticed this the last time she was forced to updated her OS a major version... the thing no longer sleeps when you tell it to or when you close the lid, it will stay connected to wifi and quite happily saturate the network downloading updates.
Only way to be sure is to power off the stupid thing.
My understanding is this is an issue with new features of all sorts of laptop/desktop devices.
For example, https://news.ycombinator.com/item?id=28639952
"Do not leave XPS laptop in any sleep/hibernate/standby mode when placed in a bag" because they stay connected to wifi and may attempt to run updates etc when the user is not expecting or prepared for that, as far as cooling.
I own an XPS, it runs Debian, it only installs updates when I tell it to.
Even if I decided to use the untended upgrades package, it wouldn't do it when I sleep the computer... that would just be stupid.
Yeah it might be unwanted behavior for your particular setup. Personally, on macOS and windows, I would prefer not to be at the computer when an update occurs - I also dont want to have to go do something else while I wait for the update. Just feels like a waste of time in my opinion. However, if I had reason to care about an update or the changes it was introducing I too would not want background updates running when I put my machine to sleep. I guess for an average user updating when the machine is not in use is a feature, while for the tech crowd that kind of behavior can mess with your preferred setup.
13 replies →
I have had this issue with Thinkpads as well. The solution was to make sure to unplug the AC power adapter before putting it to sleep and putting it in my bag. Else it would go to sleep thinking that it's still on AC power, and happily wake itself up to install updates while in my bag. If power was disconnected after putting it to sleep, it would not be able to know it was on battery power.
Or do. Then get refund when it cooks itself and buy a computer you own.
Dunno if the new MacBook Pro M1 Pro / Max are more thermally efficient or that they don't start back up in a bag but I've left mine in sleep in a sealed bag and it wasn't warm to the touch at all.
4 replies →
Yesterday my home DNS weren't resolving and noticed on PiHole that there were >30,000 requests of *.in-addr.arpa (Reverse DNS Lookup) from the iPhone+iPad of the guest to whom I gave the WiFi access and was saturating the Pi's CPU. I re-enabled rate limiting on PiHole and blocked the request with a filter.
A cursory search on the issue says Bonjour is the culprit, I'm forwarding DNS requests to my PiHole instances on my gateway and latest iOS doesn't seem to like it; I haven't faced such issue earlier and I have this setup for several years now.
https://support.apple.com/guide/mac-help/turn-power-nap-on-o...
Tried it, didn't work, I also dug out the old pmset command but it seems to have been neutered.
I'm glad I stopped using Apple stuff 10 years ago, their macs are gradually devolving into iDevices.
Sleep isn’t any different than it used to be.
“pmset -g assertions” will show you why it thinks it’s awake, it could be a silent video playing in a web browser or something. (and of course, if you can ssh in to run that it must be awake.)
1 reply →
For extra fun, if while it's sleeping it's connected to a Display Port or USB-C display, it'll wake it up everytime it wakes the wifi for its 'power naps'. Disabling them in System Prefs doesn't change this.