I am running vsftp pretty much 'out of the box', though I turned off IPv4 and have it listening on IPv6.
I have stopped ip6tables, as the simple rule to enable port 21 is not allowing gftp to connect (pasv mode, I think).
gftp to the IPv6 address, it connects and gets a directory listing. I am running gftp from my normal login userid, connecting to my normal login userid on the server.
But when I try to download or upload a file, gftp just crashes. Nothing in /var/log on either system.
Any advice?
Hi,
On Fri, Aug 15, 2008 at 4:30 PM, Robert Moskowitz rgm@htt-consult.com wrote:
I am running vsftp pretty much 'out of the box', though I turned off IPv4 and have it listening on IPv6.
[...]
But when I try to download or upload a file, gftp just crashes. Nothing in /var/log on either system.
Any advice?
Try running strace to see when gtfp crashes. Probably ~/.xsession-errors could have some useful info.
Carlos Eduardo Pedroza Santiviago wrote:
Hi,
On Fri, Aug 15, 2008 at 4:30 PM, Robert Moskowitz rgm@htt-consult.com wrote:
I am running vsftp pretty much 'out of the box', though I turned off IPv4 and have it listening on IPv6.
[...]
But when I try to download or upload a file, gftp just crashes. Nothing in /var/log on either system.
Any advice?
Try running strace to see when gtfp crashes. Probably ~/.xsession-errors could have some useful info.
Please tell me how to do this?
Others I am working with have also found gftp not working with IPv6 ftp.
Hi,
On Mon, Aug 18, 2008 at 10:00, Robert Moskowitz rgm@htt-consult.com wrote:
Please tell me how to do this?
Try running strace to see when gtfp crashes.
$ strace -tt -s 1024 -f -o /tmp/strace_gftp.txt gftp ...
Where "gftp ..." is the command line you want to run.
The output will be in /tmp/strace_gftp.txt, if you look at the end of that file you will see what gftp was doing when it crashed. You may try to send the last few lines of the file to this list (the whole file will certainly be blocked because of the attachment size) for us to help you figure out what was going on.
Probably ~/.xsession-errors could have some useful info.
$ cat ~/.xsession-errors
This should show you if there was an error in an X application, this file is basically the stderr of all the applications launched from X (IIRC).
HTH, Filipe
-
Carlos Eduardo Pedroza Santiviago -
Filipe Brandenburger -
Robert Moskowitz