ftp (PASV) timeout after exactly 3600 s

[ede_pfau]

Using Fortigate-1000 3.00-b0572(MR5 Patch 4) I have to download a zipped 1.4 GB file regularily via ftp. After exactly 3.600s the download stops and is retried, over and over again. Problem occurred because this file has increased in size over time so that (with a slow server) a download takes about 1.5 hours. remedy: I have set the session timeout to 7.200 s: config system session-ttl set default 600 config port edit 21 set timeout 7200 next end end As this affects the idle-timeout only it doesn' t help at all. I see the expiry timer stay at " 7200" or " 7199" as long as the transfer goes on. After killing the download manually the session stays in the session table for 7.200s and is removed then. Basically, I need help with 1. is there a session timeout for active sessions? 2. how could I determine that the timeout occurs not on the firewall but on the ftp client, for instance by sniffing? Any hints greatly appreciated. - Wolfgang

[abelio]

My suspicion: the ftp proxy causes this, either because of internal timeout or failure of the client comforting feature. The 3.600 s timeout value does not seem to be adjustable. Next step will be to find a bigger download from the same server and to get past 3.600s download time.

What about your script internals with the way ' wget' is called? Could you re-check this:? " ' wget' supports a timeout option, maybe you can find a switch " -T 3600 or --timeout=3600" "

[ede_pfau]

Hi, yes I' ve seen that option when I downloaded wget for Windows myself. Tried it with " -T 120" (seconds!) with no interruption, and without -T option in the original setting without timeout. BUT after 0:57 so cannot tell if it is avoiding the timeout yet. Will try again with a bigger file next week. Thanks. - Wolfgang