From: Jan Kasprzak <kas@informatics.muni.cz>
To: craig.schlenter@freemail.absa.co.za
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Linux 2.4 networking/routing slowdown]
Date: Thu, 26 Jul 2001 15:33:34 +0200 [thread overview]
Message-ID: <20010726153334.M1024@informatics.muni.cz> (raw)
In-Reply-To: <3B600EAD.3F8F9A70@isg.de> <3B6010EC.B7428A0D@isg.de> <20010726145442.K1024@informatics.muni.cz> <20010726152322.A1339@codefountain.com>
In-Reply-To: <20010726152322.A1339@codefountain.com>; from craig.schlenter@freemail.absa.co.za on Thu, Jul 26, 2001 at 03:23:22PM +0200
[Cc'd linux-kernel as well, maybe this can help someone]
craig.schlenter@freemail.absa.co.za wrote:
: Are you sure the network cards are running at full speed - perhaps
: something has decided to run at half duplex or whatever due to a network
: driver change ... how about putting the box on the network without
: having it do any routing and just doing a couple of ftp's to other local
: machines to check the speeds with 2.2 and 2.4 kernels, testing all the cards
: involved ...
The NICs on firewall are set up to 100baseTX-FD using /sbin/mii-tool
(and in 2.2. kernel, they are hardcoded to 100baseTX-FD via the boot
parameters).
The FTP from firewall to our FTP server (which is connected to the
same switch - Cisco Catalyst 2900) is slow as well (I tried to
get /pub/FILES.byname /dev/null).
-Y.
--
\ Jan "Yenya" Kasprzak <kas at fi.muni.cz> http://www.fi.muni.cz/~kas/
\\ PGP: finger kas at aisa.fi.muni.cz 0D99A7FB206605D7 8B35FCDE05B18A5E //
\\\ Czech Linux Homepage: http://www.linux.cz/ ///
--Just returned after being 10 days off-line. Sorry for the delayed reply.--
prev parent reply other threads:[~2001-07-26 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B600EAD.3F8F9A70@isg.de>
2001-07-26 12:45 ` [Fwd: Linux 2.4 networking/routing slowdown] Lutz Vieweg
2001-07-26 12:54 ` Jan Kasprzak
[not found] ` <20010726152322.A1339@codefountain.com>
2001-07-26 13:33 ` Jan Kasprzak [this message]
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=20010726153334.M1024@informatics.muni.cz \
--to=kas@informatics.muni.cz \
--cc=craig.schlenter@freemail.absa.co.za \
--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