Milambar
30-03-2011, 06:40
Went to upload a short home video to my server in Germany, 1.1Gig in size..
My server is configured to only accept ssh connections, and on a non-standard port. There is no ftp, etc. Its ssh only. So this means the use of scp or winscp to transfer files.
After 32%, the connection stalled, and my server became unreachable. Fortuntely one of my collegues also has access and he confirmed it was will up and running fine.
I noted the dns was resolving, something was just blocking the port. Rebooted the superhub, and it worked again. Had to do a nasty hack involving rsync -e 'ssh -p$port' --partial --progress.... to "resume" as scp doesnt support resume.
Got to 61% then had to reboot it again.
Got to 98% and had to reboot it again, after which, it finally completed.
Is the superhub designed to block the port like this after so much data being sent, perhaps to discourage filesharing? I was even a good net user, and waited till 3am before starting the upload.
-edit to clarify-
It was only blocking the ssh connection to that particular machine. ssh to my other 3 machines all still worked fine (they are not mine really, but belong to the company I work for, free webspace is a bonus of the job).
My server is configured to only accept ssh connections, and on a non-standard port. There is no ftp, etc. Its ssh only. So this means the use of scp or winscp to transfer files.
After 32%, the connection stalled, and my server became unreachable. Fortuntely one of my collegues also has access and he confirmed it was will up and running fine.
I noted the dns was resolving, something was just blocking the port. Rebooted the superhub, and it worked again. Had to do a nasty hack involving rsync -e 'ssh -p$port' --partial --progress.... to "resume" as scp doesnt support resume.
Got to 61% then had to reboot it again.
Got to 98% and had to reboot it again, after which, it finally completed.
Is the superhub designed to block the port like this after so much data being sent, perhaps to discourage filesharing? I was even a good net user, and waited till 3am before starting the upload.
-edit to clarify-
It was only blocking the ssh connection to that particular machine. ssh to my other 3 machines all still worked fine (they are not mine really, but belong to the company I work for, free webspace is a bonus of the job).