Cyberduck Mountain Duck CLI

#5591 closed enhancement (wontfix)

Interoperability with Topfield personal video recorder

Reported by: https://me.yahoo.com/a/y7wvk0ywyn0v8dw6ina8da4xjrc44mg-#ee052 Owned by: dkocher
Priority: normal Milestone:
Component: ftp Version: 3.8.1
Severity: normal Keywords:
Cc: Architecture: Intel
Platform: Mac OS X 10.6

Description

I'm trying to use Cyberduck to transfer files between a Mac and my Topfield TF600PVRc recorder using FTP. Topfiled uses ISO-8559-1 coding for file names and seems to have quite a limited FTP implementation.

Creating new directories will result with a preceding forward slash with a file name. Renaming files or directories doesn't work either as it will give an error that the file does not exist even though they are listed in the directory.

Some hints what is happening

With a command line ftp let's create a directory called /MP3/test:

XYzl-iMac:Users john_doe$ ftp 192.168.0.100
Connected to 192.168.0.100.
220 You will be disconnected after 60 seconds of inactivity.
Name (192.168.0.100:john_doe): DIGIBOX
331 Password required for DIGIBOX
Password:
230 OK. Current directory is /
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd MP3
250 Changed to /MP3
ftp> mkdir test
257 MKD command successful.
ftp> dir
229 Extended Passive mode OK (4194)
150 Accepted data connection from 192.168.0.10:60333
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 test
226 1 matches total
ftp>

trying to rename the newly created directory with Cyberduck:

200 NOOP command successful
CWD /MP3
250 Changed to /MP3
PASV
227 Passive mode OK (192,168,0,100,16,101)
LIST -a
150 Accepted data connection from 192.168.0.10:60798
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 test
226 1 matches total
NOOP
200 NOOP command successful
RNFR /MP3/test
550 File does not exist[[BR]]

Creating a new directory with Cyberduck called "test2" results in the following:

USER DIGIBOX
331 Password required for DIGIBOX
PASS
230 OK. Current directory is /
MKD /test2
257 MKD command successful.
NOOP
200 NOOP command successful
CWD /
250 Changed to /
STAT /
500 Unknown command.
PASV
227 Passive mode OK (192,168,0,100,16,102)
LIST -a
150 Accepted data connection from 192.168.0.10:61047
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 DataFiles
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 ProgramFiles
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 MP3
drwxrwxrwx 1 ---- ----- 0 Jan 1 00:00 /test2
226 4 matches total

Note the extra forward slash in front of the directory name.

I guess the ftp support is not up to the specs in the Topfield, but it is quite a popular personal video recorder in Europe. Would it be possible to add a compatibility feature in the ftp to handle file names in a way that the Topfield ftp-implementation would understand them correctly, or have I just missed some setting that already exists there?

Change History (2)

comment:1 Changed on Dec 24, 2010 at 10:32:53 AM by dkocher

  • Summary changed from Creating directories doesn't work correctly with Topfield personal video recorder to Interoperability with Topfield personal video recorder

comment:2 Changed on Jan 3, 2011 at 1:42:19 PM by dkocher

  • Resolution set to wontfix
  • Status changed from new to closed

We always work with absolute paths and require the server to support this.

Note: See TracTickets for help on using tickets.
swiss made software