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.
Ever since I started using Linux (almost 2 years ago now), I've noticed that uploading files via FTP tends to result in occasional stalling. Never before have I noticed a file being uploaded via FTP stall in Windows, but it seems like almost weekly something'll stall out and refuse to work in Linux. It was never a huge problem before, since if I tried again it would usually start to work fine.
However, recently I started running Gentoo Linux and have been plauged by FTP issues ever since. (I'm a web developer, so FTP issues are kinda big) Usually I just use KDE's Konqueror as an FTP client, it's always worked great for me in the past. When I noticed the constant stalling though, I pulled down gftp to test with. gftp got the file the Konqueror kept stalling on to upload, so I assumed it was just an issue with the client. Then, a few days later, I had to do some more uploading. Konqueror stalled out, so I pulled up gftp. gftp stalled out, so I pulled up the shell ftp binary. That stalled out, so I pulled up Google. After downloading yafc, I tried that, again, stalling. Where it stalls depends on the client, but each client stalls the file out at the same place. I left yafc running while I searched for information on the problem, and, as I write this post, the time elapsed on it reads 49:20. It's a 200 kB file at 25.8%; it's been at 25.8% for the last 45+ minutes. So, it isn't going to unstall itself any time soon.
Passive mode is on. There is no firewall. I'm on a router, but accessing the same FTP server works fine under Windows, so I doubt that's the cause.
Thoughts on the case and solution? To me, it seems like the issue probably lies in the Linux Kernel and the way it handles TCP stuff since the issue seems to be client-independent. Google revealed virtually nothing.
Thanks in advance,
Adam A. Flynn
Last edited by Adam A Flynn; 01-22-2006 at 08:57 PM.
is windows on the same box, and do you have problems with other network clients that use TCP, it is very unlikely that it is a Kernel problem. I'd guess it's a connectivity problem, check your cables. try copying files to and from other computers on your network see if you get the same problem. give us some more information about your network setup
Yes Windows is on the same box. Basically my computer is wired into a router which is wired into a cable modem. There are a few other windows boxes on the network. Never seen any issues with any network stuff over Windows, but I've noticed stalling out now in both my prior MDK setup and in my current Gentoo one. Odd...
The other thing I saw was that it could be my MTU setting. I had it down to 1400 bytes just to be careful; maybe bringing it up to 1472 will do something...
I'm running the e1000 driver, which should be correct for my chipset.
Also, I've noticed after more testing that the files always stall out at exactly the same place (as in, no matter what client I use, it always stops at the same spot). This spot is different for all files and none of the files appear damaged. It strikes me as odd that files are stopping at different places, but for each file always at the same place. What could that indicate?
Thanks for your help thus far, by the way, ak99505
are you running 64-bit or 32-bit, I've had problems with my internal card on my laptop when I tried 64-bit, the network connection would stop working, I put it back to 32-bit and it works fine. but that's a broadcom chipset not intel as far as I know the intel chipset has been around for awhile and should be pretty stable. but you say it's only happening when using ftp or is it happening with any connection.
Just tried to set up a DMZ to my IP address from the router... no effect. Neither passive mode on nor off has any effect. Nor does setting the type from binary to ascii.
Did a lot more testing and came to the following conclusions:
* A direct modem connection works, whereas going through the router (even with a DMZ set up) doesn't
* It doesn't work under Windows
* In Windows, I can traceroute to the server; in Linux it won't give me a traceroute
* In both OSs I can ping the server fine
* I can access the server via other protocols fine, just not FTP
* The server's FTP log says I keep timing out
The big thing, obviously, is that it works direct modem but doesn't with the router. I'm wired into the router, so transmission loss would be likely be low. What else could I configure on the router to make things work?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.