- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
This is a good example, why not all devices should be connected to foreign servers. Errors can happen everywhere. But it could end badly, if some Corporations make errors and creating trouble, which would otherwise not happen.
In the case of the 3D-printer it is not that bad (except it destroys itself or even gets on fire), also you can turn it off. But imagine a smart stove top that lights up a towel (or something similar) while nobody is home.
Not, that I think that it is not useful to have something like that, but wouldn’t it be nice, if that stuff would work locally? (with the WireGuard integration in modems, the access from outside of home with the smartphone, should also be no problem for non-tech people)
Ideally, almost no devices should be connected to the internet. Things like 3D printers, TVs with microphones/cameras, etc should be in a DMZ and have outgoing-only access to a restricted set of services.
If you’re running anything close to a professional operation, set up your site professionally. For home users, I recommend sticking with SD cards, it’s only mildly more annoying for the frequency of printing you’re likely to do.
Yep.
TVs, Fridges, Toilets, Dishwashers, Clothes Washers/Dryers, Thermostats, and a whole range of other things do not, and will never need, access to the internet.
By giving them access to the internet, you are just lighting a fuse and waiting for the bomb to go off. Maybe that bomb is personal banking details, maybe that bomb is financial in that someone cranks your AC up to 150 when you are gone for a week and come home to house full of heat damage and melt, or maybe that bomb is a 3d printer that turned on, malfunctioned, and burned your house down.
IoT is stupid.
And the worst part is, you probably can’t sue that IoT company for damages.
There’s benefits to having your 3D printer connected to the internet though. It allows you to monitor the progress and lets you cancel the print if there’s an error, potentially saving uou a lot on filament and repairs.
That being said, having them connect to centralized servers is dumb. Just add a Raspberry Pi with octoprint flashed onto it and set up your own connection if you want that feature.
You can also just VPN in. It’s not hard, and many routers have that ability today.
Octoprint is great, connecting the printer to somebody else’s computer is crazy
Yup. I’d still put it behind a VPN though, just because of the inherent dangers in starting a 3D print job remotely.
I have an nginx reverse proxy with http auth, myself. It’s such battle tested software that I trust it fully
For anyone doing similar: battle tested software is still fallible, and exploits could emerge at any point (same goes for VPNs). Be sure to set
server_tokens
tooff
, this prevents NGINX from revealing it’s version to the world, which will help protect you in case an exploit is discovered down the line.That’s a good tip. Also: have your servers auto-update weekly. You will forget.
I agree, using a VPN is generally a good idea (if the alternative is exposing it to the web directly).
Is there a guide for setting up a DMZ? I have a Nest cam for our dog (bought wayyy before Google bought them out) and use HomeKit for everything that allows it, but those devices have their own apps too so they have almost unfettered access to the net. I like having my AC on internet so I can turn it on/off when I’m not home in case I forgot to turn it on that morning (living in the PNW, so we don’t need it every day in the summer, as open windows are good enough and free), so I get home to a moderately cooled place rather than a hot box.
If you buy a fancy router (i.e. entry level professional grade, like MikroTik) or flash custom firmware (DD-WRT, OpenWRT, or Tomato), it should have the necessary features built in and have decent guides. I have a MikroTik router, but I’ve used each of the custom firmware I’ve mentioned as well.
You have a few options:
These are in order of preference top down, and reverse order of effort to setup (i.e. the first may require running new cables and/or installing new switches depending on network setup). For each option, you can configure a VPN with the network, so you can access your things remotely without having them be accessible to the outside world.
This gets trickier with cloud-based services where the only way to access things remotely is by going through someone else’s server, which is when you’d need to instruct your router to allow only certain connections in and out. I prefer to just avoid those services and go with the VPN option.
I hope that makes sense. Since you’re using cloud services, the last option will probably be the best bang for your buck. I personally go with the second because I plan to rerun cables to do the first soonish (my city is rolling out fiber, so I’ll be messing with cables anyway).
Even if it allows that set of services, if the device allows any sort of control via that service you could still end up in a bad situation.