3DPrinting
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
view the rest of the comments
I have my prusa connected to my WiFi, but it only serves up a Web page with limited control locally. You can only upload gcode, and start a print if the printer is ready to start. And it's open source so I'd expect the community to have found any issues.
You should monitor it's connections at the firewall and see if it's trying to make ANY connections outside your network, no reason for it to try making any dns queries even.
The Prusa printers have a hard coded IP address for NTP requests. There's no other way to set the time on them. At least it's to a well known public organization in the Czech Republic, but still.
Factually wrong. You can do a NAT rule to force it to whatever NTP you want. If you own the network, you can route the packets however you like.
Example from my opnsense config:
Nothing leaves my network on port 123 unless it's my own timeserver serving a response to an external request. (I actually have a proper GPS-based time server, but nothing stops you from just having a normal linux host as a timeserver or something this way either).
I do the same thing with DNS. Force all port 53 and 853 traffic to my own DNS servers. And have a wide firewall block rule for any known DoH servers.
Fair enough, I should have said that there's no other built-in way to set the time on them.
I work with 3d printers in a school that uses its own NTP server and blocks other requests. The only way I managed to set the time on the machines sort of using a raspberry pi or something, was to connect them to my phone's hotspot.
Ask the admins to setup the NAT rule.
But yeah, ultimately it's a pretty poor decision on Prusa's part to make it hardcoded. I didn't even realize my mk4 doesn't allow manually setting the time. I wonder if anyone has brought it up on the firmware repo.
I have DHCP announcing the NTP server, I haven't seen my prusa attempt to talk outside of my network. But I do see a boatload of IoT stuff ignore my local NTP all the time. Very frustrating.
I've opened an issue asking for a manual offline way to set the time, and I saw another one asking for a DHCP option.
I've tried asking the admins, and they were mad I connected the printers to the network to begin with 😅