Classic GitHub issue thread: Someone shows up and tries to explain it’s not a bug and never could have worked. Everyone else points out that it does work on other Mac hardware. Person doubles down and tries to claim that the bug was that it ever worked, and not working is the correct behavior. New Mac OS beta release fixes the bug and makes it work. Nothing related to the repo was changed.
I loved the last comment where he inferred no one knew the difference between a MAC address and a Mac computer, meanwhile he's fundamentally misunderstanding how networking works and making bizarre statements about wifi that literally everyone disagreed with him on. I bet he's still insisting he was right even though it's all fixed now because he doesn't get how VM network bridging works.
remember how there used to be people whose lifestyle was answering Stack Overflow questions? 3 years from now we're going to be looking at charts showing engagement from GitHub Lifestyle people going straight down too.
This is a standard way to form bridges in WiFi networks and does not require any ARP proxying. In practise this requires certain OS/driver/firmware/chipset combinations to work though.
But, they were wrong ... in assuming what they were saying was at all relevant. And they were so sure they knew what they were talking about and that it applied that they dismissed all the ample evidence to the contrary and also dismissed the, they assumed, delusional people pointing out the contradictions. Their initial misunderstanding was understandable given the overloaded terms but their confidence was poorly calibrated to their weakness detecting the misunderstanding.
Without looking too deep, I bet their dext wasn’t exposing necessary configuration. I’ve seen this with other third party network hardware and dext, where it was missing certain configuration for bridging to work
Unfortunately most consumers put up with it, instead of handling it like shoes, returning them to the shop for a refund, or if surviving the explosion, a lawsuit.
Classic GitHub issue thread: Someone shows up and tries to explain it’s not a bug and never could have worked. Everyone else points out that it does work on other Mac hardware. Person doubles down and tries to claim that the bug was that it ever worked, and not working is the correct behavior. New Mac OS beta release fixes the bug and makes it work. Nothing related to the repo was changed.
I loved the last comment where he inferred no one knew the difference between a MAC address and a Mac computer, meanwhile he's fundamentally misunderstanding how networking works and making bizarre statements about wifi that literally everyone disagreed with him on. I bet he's still insisting he was right even though it's all fixed now because he doesn't get how VM network bridging works.
Also classic, someone finally jumping in with a full and insightful explanation. What a turnaround!
remember how there used to be people whose lifestyle was answering Stack Overflow questions? 3 years from now we're going to be looking at charts showing engagement from GitHub Lifestyle people going straight down too.
Like that probably still open huge github issue with hundreds of comments, the one about how docker will blow your firewall wide open.
This is actually what’s interesting
So, are they gonna add official support for this in the wifi standard someday? It sounds like the way that this works is a non-standard workaround
You might be looking for https://en.wikipedia.org/wiki/Wireless_distribution_system
This is a standard way to form bridges in WiFi networks and does not require any ARP proxying. In practise this requires certain OS/driver/firmware/chipset combinations to work though.
> the bug was that it ever worked
https://xkcd.com/1172/
Your assessment is inflammatory, to my eyes.
Everything that person said was factually correct. They weren’t wrong, they simply didn’t have the whole picture.
But, they were wrong ... in assuming what they were saying was at all relevant. And they were so sure they knew what they were talking about and that it applied that they dismissed all the ample evidence to the contrary and also dismissed the, they assumed, delusional people pointing out the contradictions. Their initial misunderstanding was understandable given the overloaded terms but their confidence was poorly calibrated to their weakness detecting the misunderstanding.
I couldn't get bridged networking to work with my M5 machine and VMs running on Parallels. This thread here would seem to indicate it's a known issue (with no updates or resolution :/ ) - https://forum.parallels.com/threads/m5-macbook-air-windows-1...
The OP has a thing that solves it for many: update to a beta version.
The linked Github also states that updating to 26.6 works.
I love when things work out in the end!
(issue is fixed in the latest MacOS 26 and 27 betas)
The M5 Pro and M5 Max support Wi-Fi 7 and Bluetooth 6 via Apple's N1 wireless networking chip, while the base M5 supports Wi-Fi 6E and Bluetooth 5.3.
https://en.wikipedia.org/wiki/Apple_M5
Without looking too deep, I bet their dext wasn’t exposing necessary configuration. I’ve seen this with other third party network hardware and dext, where it was missing certain configuration for bridging to work
M5 networking stack is a mess. A lot of corporate deployments had to wait for Apple to patch up things
[flagged]
What kind of, ahem, "non consumer hardware" should I buy to run a virtual machine?
A 15 year old Thinkpad is the HN approved machine for Serious Work.
There was a good article here yesterday on Colossus.
https://news.ycombinator.com/item?id=49012309
you say that while I'm pretty sure the macbooks are the most popular laptop platform for developing software?
What hardware do you think Apple uses to build their "professional" software on?
Not sure but for CAD they use Windows:
https://www.reddit.com/r/engineering/comments/nd4ax1
> "Used to work as a mechanical design engineer at Apple. They use Siemens NX on Windows computers."
That's super weird.
Remember, if shoes were like software, they would explode while you're trying to tie the laces, because the first of the month landed on a Tuesday.
Unfortunately most consumers put up with it, instead of handling it like shoes, returning them to the shop for a refund, or if surviving the explosion, a lawsuit.