On Thu, Apr 10, 2008 at 04:02:12PM +0100, mick wrote:
On Thu, 10 Apr 2008 14:07:15 +0100 Chris G cl@isbd.net allegedly wrote:
However I can't get FTP into my NAS to work at all, all I get is a stony silence. I appreciate that there are several oddities about getting FTP to work and it *may* be that it just isn't possible with this router but it would be nice if I could get it to work.
What I have done so far is:-
Ports 20 and 21 are forwarded from "any outside IP" to the NAS which has the FTP server on it. The firewall allows ports 20 and 21 through. I have disabled the FTP access to the router completely (i.e. as I understand it I have turned the router's FTP server off, it's for Firmware updates etc.)Chris
FTP is not a good protocol to use. You have to open up way too many ports for it to work reliably and port forwarding becomes a nightmare. Why not just use sftp and forward only port 22? Much more secure too.
That's what I suspect is the problem (needing too many ports and the router not being 'FTP aware').
However sftp isn't much use as it's for non-techie windows users who occasionally want to save stuff (e.g. from cameras) while on their travels. The chances of finding sftp on an internet cafe computer are not all that great I fear.
I suspect that providing ftp access on to my hosting providers system may be the answer, I have 5Gb of disk allowance there. I can then copy across to the home machine at intervals or even run a nightly rsync.
Any other solutions for use from internet cafe or similar situations?
Are there any HTTP based tools which can save files from a remote client?