SCP and SMB Not Working

[rogersstuart]

I've ran into a few issues with my Halot Mage S image. SSH works fine but SCP only allows browsing, creating files (only creating, not adding data), and deleting files. It does not allow the transfer of any data. I tried to get sftp working using files from the linked Arch repository in the readme but none of the download links work. I found a different repository here:

http://ftp.tku.edu.tw/Linux//ArchLinux-arm/armv7h/extra/
http://ftp.tku.edu.tw/Linux/ArchLinux-arm/armv7h/core/

I only tried to get vsftpd working but ultimately failed because of a libc version mismatch. I tried changing the path to include a different version but that resulted in a different error about the kernel.

So I moved on and copied all of the smb* files from your image to mine hoping to get that working. It does work, kinda. smbclient can see my Windows share and interact with it. Mount will mount my share with SMB 1.0 enabled on my Windows machine. It's pretty fast too (considering the hardware), saturating the 100Mb connection. The problem is that this is a very inside out way of doing things. I want to mount a share of some kind on my Windows PC and drag and drop files. The issue is that smbd doesn't seem to be working. It's there in /usr/sbin and a process is running but when I try to access it from my PC I see a share called (none). Clicking on it or directly addressing the machine results in an error message. Doing it through linux results in a timeout. I've tried it with and without the internal and usb shares commented out. I've tried running smbd in interactive mode and didn't see any errors. Do you have any idea about what the problem might be? Also, do you know where I can find compatible libraries and programs? I have a feeling that I need to compile them myself but I don't even know where to begin.

During this process I bricked my machine. If anyone else has this issue make sure your flash drive partition table is MBR. I had success with a 1GB partition. While the flash drive will still mount, the machine seems to ignore compressed update files now. Instead of using the archive you can simply put the ChituUpgrade.bin file in the root of the drive and power cycle the machine. It's a little faster this way.

Here's an archive of the extracted partitions from the current version of my image: https://drive.google.com/file/d/1If9ChGWY_fJlW0rGarOtkhaVa3tT1t7T

[arsi-apli]

Try creating a symlink for scp pointing to dropbearmulti..
https://gist.github.com/mad4j/7983719

From samba itself you need all its dependencies, these can be viewed for example via ldd

[rogersstuart]

I didn't see your message before spending a few hours trying to get vsftpd working. I found an Arch Arm archive and picked the oldest version of all the files I needed from 2015 and that worked.

You can find the archive here: http://tardis.tiny-vps.com/aarm/repos/

Here's the new image file with SSH and FTP. I've completely removed the "very secure" aspect of vsftpd and set up FTP for full anonymous access.
https://drive.google.com/file/d/1_VwAM0H-DoNGt2ZYldmi5-_HKyUiOM7Q

If you want to add FTP to another image, here are the files I used:
https://drive.google.com/file/d/1lyQ40S3gGmbzhBKsZBcJV-1y18NS8P5e

I'm still not sure why SCP and SMB aren't working the way I expect them too. I did follow your link and created the scp symlink to dropbearmulti but it didn't immediately work so I'll pause here and pick this up some other time since there's a working solution for file transfers now.

[rogersstuart]

Does your printer have port 18188 open? I was able to write a small python script that manages an FTP share. When a file is uploaded it connects to port 18188 and issues a start print command. It's also possible to pause or stop the print and get status information. I'm curious if this is only useful on Creality printers or if other printers with a ChiTu board work with it too.

[rogersstuart]

I'm not sure if it's relevant to this issue but I've created a wrapper for your toolkit. I used Copilot to write a program that generates a Docker image that runs your scripts to generate a firmware file that is copied to an output directory. You can insert files into the apps.tar.gz file which is extracted and copied to the directories generated by extract_partition. scripts.py has a firmware download link that can be changed to point to another tar.gz firmware file. It's a bit hard to read because I haven't cleaned it up yet but it has been tested and works on my laptop and in a fresh VM will take it from installing WSL to generating a firmware image using one script.

https://github.com/rogersstuart/Halot-Mage-S-Toolkit