Live data from Hacker News

Recent Apple updates leading to WiFi issues?

meter.com

101–110 of 118 posts

Re: Recent Apple updates leading to WiFi issues?

#101

I (used to) work in academic IT and I hate articles like this. People would assume there is a serious problem, turn off a bunch of services, run a bunch of random-ass shell scripts, and then forget that they'd done all that and at some random point in the future discover that some feature wasn't working, and blame me.

I swear I really wish there were a way to output an entire OS's "diff" from default settings. Every preference pane, every terminal setting, every changed system file. So that you could both discover, in cases like this, what's changed -- but also simply so you could export your settings in a space-efficient way and (selectively) re-import on a new OS install.

That's honestly the main thing that made me fully switch to Linux - I use a tool called aconfmgr to do (the equivalent of) that on Arch, or NixOS would be even better now that exists.

(The main or second main thing now would be window management, the period I was using both made me like i3 now sway more and more, and grow to find macOS even with yabai or similar much more difficult and messy to use.)

Re: Recent Apple updates leading to WiFi issues?

#102
post #4

Please don't recommend people pipe curl output to a shell. Yikes.

Wait until you find out nearly every modern package manager installs stuff directly from github repos.

Docker tags (imagename:tag) aren't cryptographically secure and can be replaced by the server at any time if you aren't using imagename@sha256: format.

Re: Recent Apple updates leading to WiFi issues?

#103
post #21

Earlier quoted context omitted.

You might also try something like: sudo /usr/libexec/airportd en0 prefs AWDLEnabled=YES (Edit: see varenc's reply below) Or you could create a kext (using deprecated KPIs) that continuously blocks the interface from coming up: errno_t awdlblock_ioctl_handler(void *cookie, ifnet_t interface, protocol_family_t protocol, unsigned long ioctl_cmd, void *ioctl_arg) { if (SIOCSIFFLAGS == ioctl_cmd) { struct ifreq *ifr = (st…

Wow I didn't know about that undocumented ability to change Airport prefs! I was able to somewhat disable AWDL by doing this like you suggest: sudo /usr/libexec/airportd en0 prefs AWDLEnabled=YES And then restarting airportd so that it picks up the change: sudo launchctl kickstart -k system/com.apple.airportd This worked without having to disable SIP and modify com.apple.airportd.plist It doesn't take the awdl0 inter…

> I was able to somewhat disable AWDL by doing this like you suggest:

> sudo /usr/libexec/airportd en0 prefs AWDLEnabled=YES

Wait, why AWDLEnabled = YES? Is it like with those Cisco routers, where "do X" was usually done by negating "do inverse-of-X"? E.g. "no interface up foo" to bring down interface "foo".

Re: Recent Apple updates leading to WiFi issues?

#104
post #60

I do encounter weird Wi-Fi issues on my M1 Pro MacBook Pro. Not sure if it is related to this bug. Sometimes I am just unable to load any web pages, but I can ping those sites. I have to reboot it regularly to reconnect to the internet. The issue is most likely to occur after waking from sleep. The issue is so bad that I have to fall back to a Hackintosh at home. I originally was using an Intel-based WiFi card is gre…

> Sometimes I am just unable to load any web pages, but I can ping those sites. I have to reboot it regularly to reconnect to the internet. The issue is most likely to occur after waking from sleep.

I had that issue quite regularly on Windows and Linux back in the day, never figured out what the cause was.

Re: Recent Apple updates leading to WiFi issues?

#105
post #21

Earlier quoted context omitted.

Wow I didn't know about that undocumented ability to change Airport prefs! I was able to somewhat disable AWDL by doing this like you suggest: sudo /usr/libexec/airportd en0 prefs AWDLEnabled=YES And then restarting airportd so that it picks up the change: sudo launchctl kickstart -k system/com.apple.airportd This worked without having to disable SIP and modify com.apple.airportd.plist It doesn't take the awdl0 inter…

> I was able to somewhat disable AWDL by doing this like you suggest: > sudo /usr/libexec/airportd en0 prefs AWDLEnabled=YES Wait, why AWDLEnabled = YES ? Is it like with those Cisco routers, where "do X" was usually done by negating "do inverse-of-X"? E.g. "no interface up foo" to bring down interface "foo".

I suspect that in this case, they're telling MacOS to use the physical Ethernet port for awdl, which can't do airtime slicing.

That prevents it from doing any WiFi direct things, but otherwise would leave it functional.

Re: Recent Apple updates leading to WiFi issues?

#106

does this impact iOS wifi as well? My local HomeAssistant detects my phone on wifi for presence detection, and suddenly lately it's been all out of whack. it takes much longer to connect to wifi when I get home. and sometimes while home the presence status 'flickers', turning all the lights on/off. never used to happen

Could be. I've noticed my iPhone started to accidentally intermittently lose WiFi connection, only to reconnect again in ~3-5 seconds. I wasn't sure if this is iOS or UniFi AP bug, but I suppose it could be the former.

To add anecdata, I've been seeing the subject behavior on Meraki equipment across various firmware versions. I'm inclined to think this is an Apple-initiated issue.

Re: Recent Apple updates leading to WiFi issues?

#107

I (used to) work in academic IT and I hate articles like this. People would assume there is a serious problem, turn off a bunch of services, run a bunch of random-ass shell scripts, and then forget that they'd done all that and at some random point in the future discover that some feature wasn't working, and blame me.

Well then Apple shouldn't have shipped this bug then. Why blame individuals rather than the $2.3 trillion dollar corporation which can't get its act together.

People in the know are aware that this is just the tip of the iceberg with macOS bugs. Wifi bugs that everyone has to work around, APIs that promise Unicode NFC but aren't actually NFC, quadratic performance bugs caused by various always-on Apple services that trigger under mysterious circumstances, regressions every other minor version, the list goes on. Linux, which has orders of magnitude less money behind it, is somehow so much more robust.

But Apple won at capitalism, and the dream of most startup founders is to also win at capitalism, so this forum is filled with sycophants.

Re: Recent Apple updates leading to WiFi issues?

#108
post #54

Earlier quoted context omitted.

I just spent the last week diagnosing catastrophic Wi-Fi issues at a client location. 90% of macs wouldn’t connect to Wi-Fi, when they would association would take 45 seconds. Sometimes you couldn’t route or ping the gateway. When you could you’d get disassociated within a minute. Turning off the airdrop/anirplay interface fixes it instantly. sudo ifconfig awdl0 down It took us 5 days to figure it out. We had no less…

Was it happening to M1/M2s like the article states? Because I’m experiencing very similar issues with a 2019 model.

I work at Meter.

It does happen to older models as well with an updated MacOS but not as acutely as with M1/M2 Macs.

Re: Recent Apple updates leading to WiFi issues?

#109
"Why isn't this happening at my home? Unlike at home, in a commercial (office, warehouse, lab) environment there are many more demands placed on a Mac device’s WiFi radio as it is getting many more passive connection requests from other devices using the AWDL protocol. The more Apple devices you have on a network, the worse this issue gets."

Well, it might not happen to those rich Apple developers living in their mansions. It sure does happen to us plebes living in apartment complexes. Years ago my ThinkPad found 70 (!) WiFi networks next to me. AWDL is a nightmare here.

Re: Recent Apple updates leading to WiFi issues?

#110

Earlier quoted context omitted.

I swear I really wish there were a way to output an entire OS's "diff" from default settings. Every preference pane, every terminal setting, every changed system file. So that you could both discover, in cases like this, what's changed -- but also simply so you could export your settings in a space-efficient way and (selectively) re-import on a new OS install.

Not a full OS-diff, but there is a way to dump all the packages installed on a machine: $ mpm --output-format json installed > installed.json Source: https://github.com/kdeldycke/meta-package-manager/ With regular snapshots you can at least eliminate new installed software as the root cause of an issue. Doesn't solve the issue with preferences though.

Wow, I've been using MacUpdater but `mpm outdated` seems very useful for e.g. globally installed yarn/npm stuff too!
Post reply on HN