Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I transfer files over my LAN that are greater than 1 GB a few bytes get corrupted. I have tested with files that are under 100 MG and they transfer well. The corruption is so small that I need a program such as md5sum to detect the corruption. This is odd because I thought sftp had built-in error correction. I have used sftp with Finnix and with Gentoo and I get errors regardless. Has anyone else noticed this problem with sftp? has anyone found a workaround.
"I don't have a solution for you but I certainly admire the problem."
Can you give us a bit more on the errors? Particularly, the offsets, and also if you're running on a 32bit or 64bit machine, and any other facts you notice as you compare originals with damaged. You will probably have to use some hex comparison program to get offsets, as I think diff is too text based. If you repeat a copy (original --> sftp --> file1, original --> sftp --> file2, diff file1 file2), do file1 & file2 differ?
The 32 or 64 bit matters because of data bus width; there could be a maximum size accidentally built in to sftp somewhere by the coding constructs.
I usually use rsync for large transfers. Back when the net was less reliable, large transfers were very difficult and I never gained full trust in what we have now, even if it is better. So with rsync if the transfer works on the first time, it works. If it needs a retry or two, then there is little waste in retransmission.
Edit: and nowadays rsync works over SSH by default.
Last edited by Turbocapitalist; 06-05-2017 at 01:57 PM.
Having come at this from the hardware end, and having had a career considering component internal capacitances, logic thresholds, speeds, cable capacitance, speed & leakage vs. temperature, etc., it is a continual wonder to me that what we have is as reliable as it is, and can be pushed as fast as they are currently doing. The signal at the receiving end of a long cable (or optic fibre) is a very different looking and inferior signal from what was transmitted.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.