Modifying FileZilla to Workaround Bambu 3D Printer's FTP Issue

whalesalad

Somewhat related I am thinking of picking up a Bambu A1 as my first foray into 3d printing ... seems to be a really solid move can anyone comment?

lexicality

> I use Linux daily and don't want to switch to Windows just to connect to the printer's FTP service I wonder if the author tried using their file manager to connect? I haven't needed any kind of external file management system since switching to Linux, Dolphin just handles everything (sftp, ftp, samba, etc) for me natively in the same window.

kiproping

Instead of recompiling the source and installing it again, is there a way to monkey patch the already existing package? It seems like a few lines of code.

shevy-java

Good old FTP. I am a bit sad that it kind of died. We should have some modern FTP with super-simple everywhere implementations. Edit: Actually, some things should be fixed too if any future FTP-like protocol would be added. I never liked the difference between active mode and passive mode in FTP. A user really should never have to care about that. Things should "just work". It's only data transfer in both cases anyway.

hxbddbj

The A1 mini has FTP O_o that's actually great to hear

wqweto

Too bad FileZilla can’t be forced to use EPSV which might just work with this buggy server.

progbits

I'm guessing bambu implementation returns the server socket's listen address, and they bind to 0.0.0.0. (Typography pet peeve, how do I disambiguate that dot?) What's surprising is how this got shipped. Do the devs use some other client that has the WinSCP setting on by default, or is that feature only used by their slicer and their SDK does it by default? One theory I have is they bound the server to the printer's address originally and it behaved properly, but then changed to 0.0.0.0 later.