Hacker News Reader

Comment by exitb | Hacker News Reader

Some time ago the printers were able to communicate over both cloud and local protocols. Then, in a firmware update, they created distinct modes for those. You can still use the printers with OrcaSlicer, but in a mode that prevents being controlled by cloud too.

View on HN

Note that at least for now you can also downgrade the firmware and use the "legacy" plugin with OrcaSlicer to fully restore functionality.

This is a feature. When I enable LAN mode I do not want Bambu to be able to control my printer.

It remains astonishing to me that this is controversial. Not everyone has the knowhow to block internet access to their printer, so having a toggle in firmware is terrific. I've verified after turning it on that it never phones home. Couldn't be happier.

It’s fully understandable to want that and exactly what I use too. It still sucks for people that did want to start their prints locally and control them over the app.

Almost no one meaningfully isolates their bambu-- lots of people isolate the printer but bambu makes you run their mystery meat 'network plugin' on your host.

Unless you're running qubes or some other virtualization setup their network plugin punctures whatever airgap you put around the printer and also gives them access to your system as well.

I’ve been meaning to look into what the network plugin does more.

I see in my dns logs lots of repeated blocked requests to a Bambu labs domain whenever I have orcaslicer open. I assume it’s so many because it’s getting blocked and retrying.

I just print over lan though. Not using the Bambu servers (or the fork mentioned in OP) It works flawlessly.

The issue isn't that there's a toggle to turn off the cloud protocol in firmware. The issue is specifically that they now require you to turn off the cloud protocol if you want local access.

Reply on news.ycombinator.com