Re: ftp get corrupts file

Hello,

anagnost68 <anagnost68@xxxxxxxxx> wrote:

[...]
I experience the problem with the XP command line ftp client and the
fedora core 3 ftp command line client. Here's an example doing an mget
from fedora, notice that the retrieved file sizes are smaller than the
detected file sizes:

With "retrieved file size" you do not only mean the status
line displayed by your ftp client, but also the file size
of the actual file as shown with ls on the file system, right?
So in other words the file you downloaded is really truncated.


ftp -i 192.168.1.101
[...]
ftp> ls
227 Entering Passive Mode (192,168,1,101,80,17).
150 File status okay; about to open data connection.
drw-rw-rw- 1 user group 0 Jan 2 02:51 .
drw-rw-rw- 1 user group 0 Jan 2 02:51 ..
-rw-rw-rw- 1 user group 18705260 Jan 2 23:33 MVI_0013.avi
-rw-rw-rw- 1 user group 27172838 Jan 2 23:33 MVI_0024.avi
-rw-rw-rw- 1 user group 20330004 Jan 2 23:33 MVI_0025.avi
226 Closing data connection.
ftp> mget *
local: . remote: .
227 Entering Passive Mode (192,168,1,101,80,19).
550 Requested action not taken.
Warning: embedded .. in .. (changing to !!)
local: !! remote: !!
227 Entering Passive Mode (192,168,1,101,80,20).
550 Requested action not taken.
local: MVI_0013.avi remote: MVI_0013.avi
227 Entering Passive Mode (192,168,1,101,80,21).
150 Opening BINARY mode data connection for MVI_0013.avi (18705260
bytes).
226 Closing data connection.
18677760 bytes received in 4.5 seconds (4.1e+03 Kbytes/s)
local: MVI_0024.avi remote: MVI_0024.avi
227 Entering Passive Mode (192,168,1,101,80,22).
150 Opening BINARY mode data connection for MVI_0024.avi (27172838
bytes).
226 Closing data connection.
27164672 bytes received in 6.5 seconds (4.1e+03 Kbytes/s)
local: MVI_0025.avi remote: MVI_0025.avi
227 Entering Passive Mode (192,168,1,101,80,23).
150 Opening BINARY mode data connection for MVI_0025.avi (20330004
bytes).
226 Closing data connection.
20316160 bytes received in 4.9 seconds (4.1e+03 Kbytes/s)

What do you think?


Did you notice that the actually transferred size (as shown
by the client above) is always a multiple of 512 and that
the file size is also one time bigger?

You may also fire up ethereal/wireshark and check whether
the FTP transfers are showing something suspcious. However
I suspect it will only show that just the transferred amount
of bytes is wrong. ;-)

I guess there is a totally broken FTP server implementation
running on your NAS box. I would google for your NAS box
regarding FTP bugs and look for an update of the SW
running on the box.


Ciao, Horst
--
When pings go wrong (It hurts me too) E.Clapton/E.James/P.Tscharn
.

Relevant Pages

  • Re: - rc.DHCP.firewall (0/1) FTP on Mac behind IPTables...illegal port/cannot connect
    ... other is the DATA connection, and supports 2 modes of operation: ... since the connecting server cannot distinguish the masq box from ... your client and your masq box cannot know ... is trying to FTP to THAT, instead of your G4 client - do no be workie workie ...
    (comp.os.linux.security)
  • Re: Restricting FTP data connection port range?
    ... FTP client to passive mode when using it interactively, ... Restricting FTP data connection port range? ...
    (AIX-L)
  • Re: Restricting FTP data connection port range?
    ... Restricting FTP data connection port range? ... Not sure how you are going to restrict the port range of the client ...
    (AIX-L)
  • Re: FTP problem with data connection
    ... The need for the client to use passiv mode is well known. ... Our "problem users" do use passiv ftp ... >> Some of our users have problem with the data connection using our ftp ...
    (comp.os.linux.networking)
  • Re: FTP problem with data connection
    ... > Some of our users have problem with the data connection using our ftp ... They can login fine to the ftp servers but get "Getting file ... It would be easy to blame the client computer for bad ... This is a common problem with clients using a NAT connection, ...
    (comp.os.linux.networking)
Loading