unable to connect to VxWorks Server if rootdir is not /

[stefankaerst]

FileZilla 3.0.6 on WinXP 32bit
Server VxWorks on my dslbox

FileZilla logwindow:
Trace: ControlSocket.cpp(979): CRealControlSocket::ContinueConnect(0p22d1f4) m_pEngine=0p10dc238 caller=0p132a750
Status: Verbinde mit 192.168.0.1:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Trace: CFtpControlSocket::OnReceive()
Antwort: 220 VxWorks (VxWorks5.4.2) FTP server ready
Trace: CFtpControlSocket::SendNextCommand()
Befehl: USER admin
Trace: CFtpControlSocket::OnReceive()
Antwort: 331 Password required
Trace: CFtpControlSocket::SendNextCommand()
Befehl: PASS
Trace: CFtpControlSocket::OnReceive()
Antwort: 230 User logged in
Status: Verbunden
Trace: CFtpControlSocket::ResetOperation(0)
Trace: CControlSocket::ResetOperation(0)
Status: Empfange Verzeichnisinhalt...
Trace: CFtpControlSocket::SendNextCommand()
Trace: CFtpControlSocket::ChangeDirSend()
Befehl: PWD
Trace: CFtpControlSocket::OnReceive()
Antwort: 257 Current directory is "/RFA/"
Trace: ControlSocket.cpp(346): Failed to parse returned path. caller=0p132a750
Trace: CFtpControlSocket::ResetOperation(2)
Trace: CControlSocket::ResetOperation(2)
Trace: CFtpControlSocket::ParseSubcommandResult(2)
Trace: CFtpControlSocket::ListSubcommandResult()
Trace: state = 1
Trace: CFtpControlSocket::ResetOperation(2)
Trace: CControlSocket::ResetOperation(2)
Fehler: Verzeichnisinhalt konnte nicht empfangen werden

WireShark capture of connect:
220 VxWorks (VxWorks5.4.2) FTP server ready
USER admin
331 Password required
PASS DSLadmin
230 User logged in
PWD
257 Current directory is "/RFA/"

I created a profile for this server with type "VxWorks".
the remote directory listing does not appear - no matter if I set a remote startupdir (Standard-Verzeichnis auf Server)

hint: the connection with a simple ftp client works fine. I can do a CD / or CD /RFA/
/RFA/ is the chrooted root directory! there is no way of changing to /RFA (!)

Gruß
Stefan K.

[Tim Kosse]

VxWorks is a horribly broken platform. Not only do they use totally custom filesystem structure and listing format, it also changes from release to release.

Did you try setting the server type to all of the other available options yet?

[stefankaerst]

VxWorks is a horribly broken platform.

could you be more specific please.

Did you try setting the server type to all of the other available options yet?

yes, with the default settings it works just fine.

so, I suppose the servertype is for parsing the directory listing .. but
why is FileZilla trying to parse the PWD output from the server? it never gets used except perhaps for showing the user.
I know of ftp-servers where the users is in a chrooted env. and PWD shows the entire path (like my dslbox) but is unable to change to / . he would have to use the name of the rootdir, the server submitted after login.

Gruß/greetings
Stefan K.

[Tim Kosse]

Different VxWorks systems use different path syntax. The more broken ones don't use the "/path/with/segments/separated/by/slashes/" syntax.

The path needs to be parsed for navigating the server.