Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to get some files transferred to my new SuSe Linux 9.0 from my old SuSe 6.4 via a simple switch. Both computers access internet ftp sites without any glitches (I have downloaded tons of files from the old one, and installed the new one via ftp), but when I try to connect the two of them troubles start. No matter which way I do it (1 -> 2, or 2 -> 1) the connection starts out fine, but very soon after it slows to a crawl and then halts completely.
I have disabled the SuSe-firewall on my new SuSe 9.0 - on the account that the main router does not allow any connections from the outside (stealth mode) - and this allowed me to use ssh between the two machines. I have also tried moving the files with scp, but the same error prevents me from copying large files. Smaller files gets through only because the connection starts out fine, and takes a second or two to drop from some 200+ KB/s to a complete halt.
Now what should I look at? I have tried tcpdump, but it doesn't really enlighten me as to what the problem is about.
Yes I tried both ftp, and scp, and the same thing happens: The connection is succesfull, but the bandwidth quickly falls to a halt. Even if I'm the only one using the 10/100 MBit network switch.
What's even more worrisome (if I have understood anything), is that my 'ifconfig -a' (it shouldn't really matter from which machine) says some 264 collisions only, and that was after many, many trials.
I'm most bewildered, but must admit that I'm not an expert on the tcpwrappers in inetd and xinetd respectively used on the two machines.
Only my new machine uses iptables. When sending via ncftp to the new machine, the respons is:
Chain INPUT (policy ACCEPT 115 packets, 71579 bytes)
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
Chain OUTPUT (policy ACCEPT 121 packets, 8372 bytes)
No that just means that sshd is not started.
This has nothing to do with your original problem though. The only reason I was asking you to try scp was to rule out ftp as the problem. Since it is occurring on both ftp and scp I move to firewalls that might be throtling the connection down to prevent a DOS attack. Since that does not appear to be the problem let more towards datalink level. What is the output of
On both machines.
Do you have a crossover cable?
I think the source of trouble has been located and fixed: xinetd halts after a few seconds because it tries to start up as user '--default--'. When this value is set to 'root' in the conf. file (/etc/xinetd.d/services) xinetd starts up just fine. This became obvious when pressing "ctrl-alt-f10" for a view of the system logs (btw: can't these log-outputs be seen another way?).
Now if only I could get my old ethernet card up and running (for no apparent reason it has stopped working because the dhclient times out waiting for a valid dhcp-server response) so that I could verify the succes, my weekend would be saved.
Thanks a lot for all Your help. I'll reports back as soon as I know more.