Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am running ubuntu on various computers on a home wireless network. Some are on 9.04x64, some 10.04x64 and one 9.04x32.

Running scp with a large file starts out at 2.1 mbps and drops down to about 200k, stalling and dropping until the transfer is complete. I've noticed this when I have a secure shell open on any of these servers as well.

I have tried this with 2 different routers, both brand new, different brands.

share|improve this question
    
I would look into using rsync for transfering large files. Especially if you do this frequently. If rsync dies, mid transfer, when you run it again, it won't copy /all/ of the data again. It will fix amy corruption on the receiving end, and start where it stopped. –  cpbills May 28 '10 at 4:28
    
yeah, rsync is unbelievably slow too - i'm running: rsync -azvv -e ssh charles@192.168.1.140:./bigfile.tar.gz . –  coleifer May 29 '10 at 4:11
    
Don't forget to pass --partial to rsync, or it will delete any partially-transferred large files when the connection dies. –  Marius Gedminas Jul 30 '10 at 11:44
    
What's the packet loss like between the two machines? What's the packet loss like when you use bigger packets (sudo ping -s 2000 otherhost)? –  Marius Gedminas Jul 30 '10 at 11:45
    
using the -z option when you're transferring .gz files will be pointless. You're not likely to notice the overhead, but your system will try to recompress it again on the fly. Not relevant to your current issue, just putting that out there. –  UtahJarhead Apr 17 '12 at 2:49
show 1 more comment

2 Answers

I would suspect wifi issues, but that can be ruled out by just connecting them together via ethernet (either through a switch or cross-over cable).

share|improve this answer
add comment

Have you tried a transfer between two of the systems while they were directly connected to each other? That's the only sure-fire way to rule out the network gear as a source of the problem.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.