FTP SSL negotiation leads to hanging board?

[birkenfeld]

I've been wondering why I can't connect to the Wipy with the "ftp" or "lftp" clients on my home machine, while from a work laptop it works. Turns out that at home the ftp is built with SSL support and will try to negotiate SSL. The dialog looks like

Code: Select all

Connected to 192.168.1.78.
220 Micropython FTP Server
Name (192.168.1.78:gbr): micro
332 

and then the board is hanging (no telnet login possible) until reset. WIth tcpdump I saw that the client is sending

Code: Select all

AUTH SSL

before getting the 332 reply.

I can switch off SSL easily now that I know it, but it might be good to investigate the source of the hang. Thanks!

[danicampora]

FTP on the WiPy server is simple FTP, so SSL, that's the reason.

[birkenfeld]

Would be nice to to freeze the board, though...

[danicampora]

I agree. I'll check with back with TI, because this is looks like an issue in the underlying socket layer.