Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Recent Apple updates leading to WiFi issues?

meter.com

Post reply on HN
Print view View original

61–70 of 118 posts

Re: Recent Apple updates leading to WiFi issues?

#61

Post by jetsnoc »

I stream at a pretty high bandwidth a remote system for gaming. I noticed this immediately. I disabled location sharing and it got a little better. I noticed that everytime my spouse started using his iPhone or opened his M2 Air to do something that my game stream seized. I guessed at something like this being the issue and disabled Airdrop. The problem immediately went away. I cursed about software quality in 2022 but also had a "HugOps" moment where, ... I get it. This stuff is hard stuff and most of the time I don't experience serious defects like this after upgrading OS X.

I still have an issue every now again and for whatever reason a reboot addresses it. I will ifconfig down the interface next time. I suspect that will resolve it.

Re: Recent Apple updates leading to WiFi issues?

#62

Post by est31 »

dwohnitmok wrote: post #40
crazygringo wrote: post #37

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.

This has gotta be some sort of HN meme at this point but... NixOS gives you this (with the tradeoff of course of a really steep learning curve and very opinionated packaging structure)!

Tbh in the hypothetical scenario where all of a company's configuration were handled via nix, you'd be staring at tens to hundreds of thousands of lines of company-custom .nix files where one single line might cause the bug you are encountering.

Re: Recent Apple updates leading to WiFi issues?

#63

Post by saagarjha »

LASR wrote: post #59

I’ve been noticing this for a while. Both my laptop and my wife’s have this problem. Both are M1. Both our iPhones seem to have similar issues. I went mad trying to figure it out with my router/APs etc. I was certain there is no way it could be Apple’s issue. But in hindsight this makes sense. Especially so, if Apple is sharing some driver logic between M1 laptops and A16 SOCs on the phones. Edit: I want to add that…

AWDL steals time from your Wi-Fi connection; it doesn’t drop requests.

Re: Recent Apple updates leading to WiFi issues?

#64

Post by saagarjha »

chazeon wrote: 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…

Have you tried seeing if it connects in another browser?

Re: Recent Apple updates leading to WiFi issues?

#65

Post by saagarjha »

efficax wrote: post #17
bink wrote: post #4

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

eh it's fine. sure, technically speaking you're giving your machine over to whoever wrote that script. they could do anything! but actually, the script is usually useful and safe. Like this one.

I took a peek at the script and I don’t think I want anyone who writes code like that coming anywhere near my machine if I can help it.

Re: Recent Apple updates leading to WiFi issues?

#66

Post by rkeene2 »

lilyball wrote: post #11
tristor wrote: post #8

Earlier quoted context omitted.

Is this true? I hadn't even noticed, because I assign every device a static DHCP assignment so I can categorize devices numerically. That is really messed up, and akin to what Google does with TCP/HTTP for connections to google.com in order to ensure it gets first byte faster. Companies are doing all sorts of "performance hacks" that just straight our break standards, and therefore break interop. I know for Apple dev…

Apple isn't breaking a standard. If the IP address was reassigned to another device it'll just get told that upon attempting to use it.

The alleged violation is using the IP after the lease expires and before the issuance of a new lease. I don't know if that's true, since most DHCP clients request a new IP long before their lease expires to avoid this.

Re: Recent Apple updates leading to WiFi issues?

#67

Post by jiggawatts »

crazygringo wrote: post #37
LeoPanthera wrote: post #15

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.

I don't know why people are dismissing this as non-viable or complex.

For example, a typical Windows deployment is 15-20GB after being extracted from an ISO image that's essentially static. There's monthly updates, which are also monolithic multi-GB patches that wholesale replace system files.

This is basically like a Docker image, but with the Kernel and drivers included in the base layer...

.. but without any of the niceties of dockerfiles, such as precisely tracking what differences have been applied!

The Windows registry could be split into a "system base hive", a "patch hive", and then a "customisations hive" on top.

Similarly, Linux filesystems could keep a base copy of the "/etc" directory and then any changes on top in something like a unionfs or docker image like overlayfs.

Modern phone operating systems more-or-less work like this, so it's definitely possible.

In the distant past of 40MB hard drives, this approach would have been wasteful. In the era of 5GB patches... does it really matter?

Re: Recent Apple updates leading to WiFi issues?

#68

Post by nchase »

I believe that the issue is real, but this article suggests a mind-bogglingly unsafe solution.

The steps include downloading a remote script, then entering the password of a privileged user.

Goodness, it would be a shame if someone were to change the contents of that remote script.

Re: Recent Apple updates leading to WiFi issues?

#69

Post by nequo »

crazygringo wrote: post #37
LeoPanthera wrote: post #15

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.

This would be great. In principle, this should be a `diff -ur` of /etc against the default /etc of the OS. Some complications ensue as the user’s own dotfiles might override some things, too.

Re: Recent Apple updates leading to WiFi issues?

#70

Post by anilv »

more_corn wrote: post #33
LeoPanthera wrote: post #15

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 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…

I work at Meter.

We’ve seen this repeatedly across different types of spaces and have had teams spend similar amounts of time to get to know what’s going on underneath.

Post reply on HN