MT32-pi freezes when performing an FTP action

[retro]

I have enabled networking and FTP on my MT32-pi, and I am able to logon to it successfully via Filezilla.

It is connected via Ethernet to a Gigabit Ethernet Switch, and a static IP address is assigned in mt32-pi.cfg.

Any attempts to upload or download any files via FTP does not work.

Below is the Message Log from Filezilla

Status: Connecting to 192.168.2.154:21...
Status: Connection established, waiting for welcome message...
Status: Plain FTP is insecure. Please switch to FTP over TLS.
Status: Server does not support non-ASCII characters.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
Status: Retrieving directory listing of "/SD"...
Status: Directory listing of "/SD" successful
Status: Starting download of /SD/mt32-pi.cfg

It does not go beyond the "starting download" action.

Filezilla is already configured to upload and download in Binary only.

Below is the network section from my mt32-pi.cfg. Hostname, username, and password sections omitted for obvious reasons.

mode = ethernet
dhcp = off
ip_address = 192.168.2.154
subnet_mask = 255.255.255.0
default_gateway = 192.168.2.1
dns_server = 192.168.2.4
rtp_midi = on
ftp = on

Please advice

[Malor]

FTP is a really old and weird protocol that uses a separate data channel on a separate socket to do transfers. Make sure any firewalling between you and it is turned off. That includes on the m32pi itself. Windows' own firewalling could potentially interfere as well, but I definitely wouldn't turn that off.

There's nothing special about the protocol, it's just a method to transfer files, so you can potentially save a bunch of troubleshooting pain by switching to ssh and using the scp utility to transfer files. You don't get a direct browse function in the same way, and have to do more typing, but file transfers over ssh are very robust. And command-line clients are built right in to Windows 10.

Filezilla doesn't seem to support ssh/scp, but lots of graphic utilities do. One decent one is MobaXTerm, which is sort of a remote-access Swiss Army Knife. It's payware, but the free version will support four connections, so you can use it for this easily.

Using Windows 10's built-in utilities, to get a remote shell, you open a command prompt and type:

Code: Select all

ssh username@hostname

or

Code: Select all

ssh username@ipaddress

That will let you navigate around the filesystem, and you can do remote edits with a textmode editor. Nano is good if you don't know anything else. (eg, ssh into the machine, cd to the right directory, nano mt32-pi.cfg. If nano's not there, try pico, which is very similar: pico mt32-pi.cfg. If Pico's also not there, post back and we'll try to figure out what's available. (I don't have an MT32pi yet, still trying to source the actual Pi.)

To copy files, it's similar syntax to unix cp. You'd type:

Code: Select all

scp username@hostname:/path/to/mt32-pi.cfg .

The trailing period means 'here', the current directory on the local machine. Then you'd edit the file however you wanted, and:

Code: Select all

scp mt32-pi.cfg username@hostname:/path/to

Overall, I would recommend sshing into the mt32-pi and using a local editor. This avoids the problems with Windows text and Unix text not being the same thing. By doing the editing in Unix, everything is straightforward and just works. You can potentially munge things up by copying to Windows, editing with a standard Windows editor, and then copying the file back. It's fixable, but kind of a pain.

ssh plus nano or pico should be pretty easy, and relatively foolproof.

[retro]

Here's the weirdest thing... I simply switched from Ethernet to Wifi for the mt32pi, and everything works perfectly. No other settings were changed.

[Malor]

That implies that it was firewalling, and that the firewall scripts are buggy.

[MorkMikael]

i have the same problem. my router is a netgear.

[retro]

i have the same problem. my router is a netgear.

I was using a DLink Gigabit Ethernet switch connected to an Asus RX-A3000 router.

Did the problems go away when you switch to Wifi for the MT32-pi?

[MorkMikael]

yes it did

[d0pefish]

[...]
ssh plus nano or pico should be pretty easy, and relatively foolproof.

mt32-pi is a bare-metal project, not a Linux box. There is no OS, no firewall rules, no SSH, no nano, and no pico.
Absolutely none of this applies.

@retro and @MorkMikael

You are not the first to report a possible FTP failure with Ethernet (but working OK with Wi-Fi).
To be honest, Ethernet doesn't get tested often, and it sounds like a bug. I'll investigate this and get back to you.

[d0pefish]

Please try FTP over Ethernet with the attached test build.

Just replace the kernel*.img files on your Pi's SD card with the ones from the zip archive.

[MorkMikael]

it works for me now. can ftp to it, and use putty to get the server info.but check with other too.
tested with WinSCP,putty,and telnet from the mister to mt32-pi and got the mt32-pi info

[retro]

Please try FTP over Ethernet with the attached test build.

Just replace the kernel*.img files on your Pi's SD card with the ones from the zip archive.

FTP works perfectly with Ethernet now via Filezilla

However, further testing revealed this error message with the mt32pi_updater script

cTMXOwK.png (18.55 KiB) Viewed 2301 times

[d0pefish]

Don't worry about the script for now; that's just because you are running a test build and the script can't understand the embedded version information (it's a Git commit hash rather than the usual xx.yy.zz).

I'll push a new release of mt32-pi shortly and then the script should work after manually updating to that new version.
Thanks for testing!

[d0pefish]

mt32-pi v0.11.3 has now been released with the Ethernet fix included.

Additionally, the updater script has received several fixes (especially for Windows users and Windows-based terminals).

If you are running the test build above, you should be able to re-run the updater script without touching the Pi.
The script should self-update and then handle the invalid version number and update the Pi anyway.

Running the script a second time should then show the Pi as up-to-date.

Let me know how you get on.

[retro]

Vo5SEW1.png (46.59 KiB) Viewed 2147 times

Worked like a charm!

[d0pefish]

Now we're talking.

Thanks for reporting the issue and testing the fix