• OpenWrt is so much more efficient than other linux distros.
• On a single core 580MHz cpu (with moonraker, klippy, nginx and mjpg-streamer) I get ~20-25% cpu load while idle/not printing and max 35-40% cpu load while printing and watching stream (640x480 30fps mjpeg).

• I've tried octoprint on this box as well but unfortunately it was too resource intensive. Test prints speak for themselves.

• A router box device released by Creality in 2020 meant to add cloud based remote control to your printer. Creality Cloud App is a contraption between social media and 3d printing that you have to use to be able to print and monitor.

  Sounded like a good idea. Unfortunately, the unpolished idea was not very well received by the public. Creality recently (July 2021) added Cura integration and custom gcode upload. Webcam support finally got released but it seems to only work with their new proprietary webcam. Everything is still cloud based and you can't use it offline. This raised a lot of concerns in terms of privacy and transparency. Putting all your trust in a company is not necesarily the best idea and although they seemed to have improved the app and user experience the full control is not in the user's hands yet.

  It's hard to please everybody when creating a product/service but actually listening to the public's feedback is a good start. People need privacy, full control and reliability to actually consider using the product over the alternatives. Klipper and it's UI clients come as open source and 100% transparent alternatives to remote printing.

• A Linux OS built for embeded devices, routers especially. Light, Open Source with a great community and
  packages that gives your device the freedom it deserves.

• A 3d-printer firmware. It runs on any kind of computer taking advantage of the host cpu. Extremely light on cpu, lots of features

• These are free and open-source Klipper web interface clients for managing your 3d printer.

• A Python 3 based web server that exposes APIs with which client applications (fluidd or mainsail) may use to interact with Klipper. Communcation between the Klippy host and Moonraker is done over a Unix Domain Socket. Tornado is used to provide Moonraker's server functionality.

• Duet Web Control is a fully-responsive HTML5-based web interface for RepRapFirmware. Stephan3 built a socket to make it communicate with klipper as well (klipper is not a RepRapFirmware). This is a standalone webserver and client interface - so no need for moonraker or nginx.

This method uses 2 scripts, one to format a micro sd card <= 8GB and make it extroot, and another one that fetches and installs everything from the internet.

• Make sure you've flahsed/sysupgraded latest .bin file from /Firmware/OpenWrt_snapshot/ or from latest release.

• Connect to the OpenWrt access point

• Access LuCi web interface and log in on 192.168.1.1:81

• (optional but recommended) Add a password to the OpenWrt access point: Wireless -> Under wireless overview EDIT the OpenWrt interface -> Wireless Security -> Choose an encryption -> set a password -> Save -> Save & Apply

• (optional but recommended) Add a password: System -> Administration -> Router Password

• ❗If your home network subnet is on 1 (192.168.1.x), in order to avoid any ip conflicts, change the static ip of the box LAN from 192.168.1.1 to something like 192.168.3.1. To do that access the luci webinterface -> Network -> Interfaces and edit the static ip -> Save -> press the down arow on the Save&Apply button -> Apply Unchecked. You can now access luci on the new ip and continue configuring Client setup.

• Connect as a client to your Internet router: Network -> Wireless -> SCAN -> Join Network -> check Lock to BSSID -> Create/Assign Firewall zone then under custom type wwan enter -> Submit -> Save -> Save & Apply

• Connect back to your router and either find the new box's ip inside the DHCP list.

• ❗ Access the terminal tab (Services -> Terminal) ❗ If terminal tab is not working go to Config tab and change Interface to the interface you are connecting through the box (your wireless router SSID for example) -> Save & Apply.

• Use these commands to download and run the 1_format_extroot.sh script:

   cd ~
   wget https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/scripts/1_format_extroot.sh
   chmod +x 1_format_extroot.sh
   ./1_format_extroot.sh
   
  

• You'll be prompted to reboot: type reboot

• Use these commands to download and run the 2_script_manual.sh script:

   cd ~
   wget https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/scripts/2_script_manual.sh
   chmod +x 2_script_manual.sh
   ./2_script_manual.sh
  
  

• Follow the prompted instructions and wait for everything to be installed. If the script exits before installation is complete, complaining about missing resources, try running it again.

• You can remove the scripts, if you want, when done: rm -rf /root/*.sh

• When done and rebooted use http://openwrt.local or http://<your-box-ip> to access the Klipper client. Depending on your network configuration the no-ip may work, but the ip will always connect, providing nginx is up and running!

• Use Mainsail or Fluidd to upload your printer.cfg Or use your method of choice to place it in /root/printer_data/config

• delete these blocks from your printer.cfg: [virtual_sdcard], [display_status], [pause_resume] since they're included inside fluidd.cfg/ mainsail.cfg

• add these lines inside your printer.cfg depending on your klipper client (mainsail/fluidd):

• Fluidd: [include fluidd.cfg] [include timelapse.cfg]

• Mainsail: [include mainsail.cfg] [include timelapse.cfg]

• Under [mcu] block change your serial port path according to this[Optional]

• Build your klippper.bin mainboard firmware using a linux operating system. It cannot be built using OpenWrt on the box (follow printer.cfg header for instructions)

• Flash your mainboard according to the printer.cfg header

• Do a FIRMWARE RESTART inside fluidd/Mainsail

• Done

Notes:

• If the box doesn't connect back to your router wirelessly connect to it with an ethernet cable and setup/troubleshoot wifi.
• Check here for how to set your TIMELAPSE_TAKE_FRAME macro inside your slicer layer change.

❗ Although this is an OpenWrt snapshot, it works seamlessly as long as the core package feed points at the correct tag for the firmware version in this repo.

opkg update && opkg install block-mount kmod-fs-ext4 kmod-usb-storage kmod-usb-ohci kmod-usb-uhci e2fsprogs fdisk
DEVICE=$(awk '$2 == "/overlay" {print $1}' /etc/mtab)
uci -q delete fstab.rwm
uci set fstab.rwm="mount"
uci set fstab.rwm.device="${DEVICE}"
uci set fstab.rwm.target="/rwm"
uci commit fstab
mkfs.ext4 /dev/mmcblk0p1
DEVICE="/dev/mmcblk0p1"
eval $(block info "${DEVICE}" | grep -o -e "UUID=\S*")
uci -q delete fstab.overlay
uci set fstab.overlay="mount"
uci set fstab.overlay.uuid="${UUID}"
uci set fstab.overlay.target="/overlay"
uci commit fstab
mount /dev/mmcblk0p1 /mnt
cp -f -a /overlay/. /mnt
umount /mnt
reboot

opkg update && opkg install swap-utils
dd if=/dev/zero of=/overlay/swap.page bs=1M count=512
mkswap /overlay/swap.page
swapon /overlay/swap.page
mount -o remount,size=256M /tmp

rm /etc/rc.local;
cat << "EOF" > /etc/rc.local
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.

###activate the swap file on the SD card
swapon /overlay/swap.page

###expand /tmp space
mount -o remount,size=256M /tmp

exit 0
EOF

opkg install git-http htop unzip;
opkg install --force-overwrite gcc;
opkg install patch;
opkg install python3 python3-pip python3-cffi python3-dev python3-greenlet python3-pillow python3-yaml;
pip install --upgrade pip;
pip install --upgrade setuptools;
pip install python-can configparser;
opkg install python3-tornado python3-distro python3-curl python3-zeroconf python3-paho-mqtt python3-requests ip-full libsodium;
pip install pyserial-asyncio lmdb streaming-form-data==1.15.0 inotify-simple libnacl preprocess-cancellation apprise ldap3 dbus-next importlib-metadata;

• Install nginx with opkg install nginx-ssl

• 6.1 Clone Klipper inside ~/ - git clone --depth 1 https://github.com/Klipper3D/klipper.git.
• 6.2 Use provided klipper service and place inside /etc/init.d/

wget -q -O /etc/init.d/klipper https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/Services/klipper
chmod 755 /etc/init.d/klipper

• 6.3 Enable klipper service:

/etc/init.d/klipper enable

• 6.4 Prepare your printer.cfg file:

mkdir ~/klipper_config ~/klipper_logs ~/gcode_files

• Locate your .cfg file inside ~/klipper/config/ copy it to ~/klipper_config and rename it to printer.cfg

• Inside printer.cfg under [mcu] replace serial line with serial: /dev/ttyUSB0

• Add either [include mainsail.cfg] or [include fluidd.cfg] to the top of the printer.cfg file depending on which front end you chose

• 6.5 Restart klipper - do service klipper restart or /etc/init.d/klipper restart

• 6.6 Build klipper.bin file - Building is not mandatory to be done on the device that hosts klippy. To build it on this box you would need a lot of dependencies that are not available for OpenWrt so I just used my pc running ubuntu: On a different computer running linux (or VM or live USB) -> Clone klipper just like you did before -> cd klipper -> make menuconfig -> use the configurations specific to your mainboard (Check the header inside your printer.cfg file for details). :exclamation: use custom baud: 230400. By default 250000 is selected. If you want/need that baud, remove the python-pyserial package and install this version of pyserial instead - check Requirements directory for details about installation process. -> once configured run make -> if succesfull the firmware will be inside ./out/klipper.bin -> flash the mainboard:(check header of printer.cfg again - some mainboards need the .bin file renamed a certain way) copy the .bin file on a sd card -> plug the card with the printer off -> turn printer on and wait a minute -> Done (Depending on your mainboard/printer/lcd you will probably not have a sign that the mainboard got flashed so don't worry) - if at the end of this guide the client cannot connect to the klipper firmware usually the problem is with the .bin file building or flashing process.

• 7.1 Clone Moonraker

cd ~
git clone https://github.com/Arksine/moonraker.git

• 7.2 Use provided moonraker.conf file and download chosen client

For fluidd:

mkdir ~/fluidd
wget -q -O /root/fluidd/fluidd.zip https://github.com/cadriel/fluidd/releases/latest/download/fluidd.zip && unzip /root/fluidd/fluidd.zip -d /root/fluidd/ && rm /root/fluidd/fluidd.zip
wget -q -O /root/klipper_config/moonraker.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/moonraker/fluidd_moonraker.conf
wget -q -O /etc/nginx/conf.d/fluidd.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/nginx/fluidd.conf

For Mainsail:

mkdir ~/mainsail
wget -q -O /root/mainsail/mainsail.zip https://github.com/meteyou/mainsail/releases/latest/download/mainsail.zip && unzip /root/mainsail/mainsail.zip -d /root/mainsail/ && rm /root/mainsail/mainsail.zip
wget -q -O /root/klipper_config/moonraker.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/moonraker/mainsail_moonraker.conf
wget -q -O /etc/nginx/conf.d/mainsail.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/nginx/mainsail.conf

Note: The [update_manager] plugin was commented out since this is curently only supported for debian distros only. For now, updating moonraker, klipper, fluidd or mainsail should be done manaully.

Don't forget to edit(if necessary) the moonraker.conf file you copied inside ~/klipper_config under trusted_clients: with your client ip or ip range (client meaning the device you want to access fluidd/mainsail from). Check the moonraker configuration doc for details.

• 7.3 Use provided moonraker service and place inside /etc/init.d/

wget -q -O /etc/init.d/moonraker https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/Services/moonraker
chmod 755 /etc/init.d/moonraker
/etc/init.d/moonraker enable
/etc/init.d/moonraker restart

• 7.4 Download the rest of the nginx files inside /etc/nginx/conf.d*

wget -q -O /etc/nginx/conf.d/upstreams.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/nginx/upstreams.conf
wget -q -O /etc/nginx/conf.d/common_vars.conf https://raw.githubusercontent.com/shivajiva101/KlipperWrt/v4.4/nginx/common_vars.conf

Inside /etc/nginx/conf.d you should have fluidd.conf OR mainsail.conf alongside common_vars.conf AND upstreams.conf (those 2 files are common for mainsail and fluidd)

Note! You need to use either fluidd.conf or mainsail.conf file depending on your chosen client. Don't use both .conf files inside /etc/nginx/conf.d/. If you want to test both clients and easly switch between them check the ! How to switch between fluidd and mainsail: below.

Note! It's ok to keep both client directories inside /root/ as these are static files. Careful with the .conf file inside /etc/nginx/conf.d.

• 7.6 Restart nginx with service nginx restart and check browser if http://your-ip brings you the client interface (fluidd or mainsail).

❗ How to switch between fluidd and mainsail:

1. switch between mainsail.confand fluidd.conf file inside /etc/nginx/conf.d (make sure the other one gets renamed to a different extension. eg: *.conf_off or moved to a different folder.)
2. Switch between mainsail and fluidd moonraker.conf files inside ~/klipper_config. Find them inside my repo under moonraker directory.
3. Restart moonraker and nginx services: service moonraker restart and service nginx restart

• install video4linux utilities: opkg update && opkg install v4l-utils
• use commands: opkg update && opkg install mjpg-streamer-input-uvc mjpg-streamer-output-http mjpg-streamer-www
• connect a uvc webcam, configure /etc/config/mjpg-streamer to your likings, enable and restart service:

/etc/init.d/mjpg-streamer enable /etc/init.d/mjpg-streamer restart

• put the stream link inside the client(fluidd/mainsail) camera setting: http://<your_ip>/webcam/?action=stream

• To change your hostname go to /etc/config/system and modify option hostname 'OpenWrt' to your likings.
• To use your hostname in browser and ssh instead of the ip do:

opkg update
opkg install avahi-daemon-service-ssh avahi-daemon-service-http
reboot

• Instead of http://your-ip use http://your_hostname.local

• for Klipper - check the requirements.txt file.

• 6.1 Clone Klipper inside ~/ - do opkg install git-http unzip then git clone --depth 1 https://github.com/KevinOConnor/klipper.git.
• 6.2 Use provided klipper service and place inside /etc/init.d/ - find it inside Services -> klipper
• 6.3 Enable klipper service: Everytime you create a service file you need to give it executable permissions before enabling it. For klipper do chmod 755 klipper. You can enable it now by /etc/init.d/klipper enable
• 6.4 Prepare your printer.cfg file - do mkdir ~/klipper_config and mkdir ~/gcode_files . Locate your .cfg file inside ~/klipper/config/ copy it to ~/klipper_config and rename it to printer.cfg - Inside printer.cfg under [mcu] replace serial line with serial: /dev/ttyUSB0 and add a new line: baud: 230400 - (check requirements if you want/need 250000 baud)
• 6.5 Restart klipper - do service klipper restart or /etc/init.d/klipper restart
• 6.6 Build klipper.bin file - Building is not mandatory to be done on the device that hosts klippy. To build it on this box you would need a lot of dependencies that are not available for OpenWrt so I just used my pc running ubuntu: On a different computer running linux (or VM or live USB) -> Clone klipper just like you did before -> cd klipper -> make menuconfig -> use the configurations specific to your mainboard (Check the header inside your printer.cfg file for details). :exclamation: use custom baud: 230400. By default 250000 is selected. If you want/need that baud, remove the python-pyserial package and install this version of pyserial instead - check Requirements directory for details about installation process. -> once configured run make -> if succesfull the firmware will be inside ./out/klipper.bin -> flash the mainboard:(check header of printer.cfg again - some mainboards need the .bin file renamed a certain way) copy the .bin file on a sd card -> plug the card with the printer off -> turn printer on and wait a minute -> Done (Depending on your mainboard/printer/lcd you will probably not have a sign that the mainboard got flashed so don't worry) - if at the end of this guide the client cannot connect to the klipper firmware usually the problem is with the .bin file building or flashing process.

• Download cd ~ git clone https://github.com/Stephan3/dwc2-for-klipper-socket

• Edit dwc2.cfg - set the web_root: path to absolute path: /root/sdcard/web

• Create dwc socket service Create a dwc file inside /etc/init.d/ with the contents of the dwc file inside my repo: Services->dwc Give it executable permissions: chmod 755 /etc/init.s/dwc Enable it: /etc/init.d/dwc enable

• Download dwc version 3 web interface

mkdir -p ~/sdcard/web
cd ~/sdcard/web
wget -O DuetWebControl-SD.zip https://github.com/Duet3D/DuetWebControl/releases/download/3.1.1/DuetWebControl-SD.zip
unzip *.zip && for f_ in $(find . | grep '.gz');do gunzip ${f_};done
rm DuetWebControl-SD.zip

• Restart dwc socket service: service dwc restart or /etc/init.d/dwc restart
• Test: https:://<your_ip>:4750

• To change your hostname go to /etc/config/system and modify option hostname 'OpenWrt' to your likings.
• To use your hostname in browser and ssh instead of the ip do:

opkg update
opkg install avahi-daemon-service-ssh avahi-daemon-service-http
reboot

• Instead of http://your-ip use http://your_hostname.local