From: "Dennis Grant" <trog@wincom.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT] *SOLVED* Slow FTP Transfers between 2.4 machines
Date: Tue, 03 Dec 102 01:08:33 -0500 [thread overview]
Message-ID: <3dec4aff.50ae.0@wincom.net> (raw)
>> This _might_ be OT... certainly I'm not entirely ready to lay
>> this at the feet of the kernel just yet.
Oi, and a damn good thing I didn't too.
Mea culpa. I'm a dumbass. :(
The problem turned out to be this:
Box A gets its IP address and other routing information from DHCP, via the cable
modem
Box B gets its IP address and other routing information from DHCP, via the cable
modem
See where this is going?
Yup, all traffic between the two boxes was going via the cable modem and the
upstream gateway. The cable modem has an upload limit of roughly 40k/sec, so...
there it is.
Adding the appropriate routing information to each box to tell it that the other
was local resulted in an immediate jump in FTP transfer rates to 1000k/sec,
which I think is the max speed on a 10mbs line.
Doh!
I'll just slink off into this corner over here and be quiet for a while.
Thanks to "ManMower" who caught the problem, and to everybody else who responded.
DG
reply other threads:[~2002-12-03 6:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3dec4aff.50ae.0@wincom.net \
--to=trog@wincom.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).