From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: "Jacek Popławski" <jpopl@interia.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.20 vs 2.4.17 on 486 server
Date: 08 Jan 2002 21:59:58 -0500 [thread overview]
Message-ID: <1010545201.1258.1.camel@aurora> (raw)
In-Reply-To: <20020108220229.A13462@localhost.localdomain>
In-Reply-To: <20020108220229.A13462@localhost.localdomain>
I believe that the ipchains compatibility in 2.4.17 is a hack. You
really should use iptables and not use the ipchains in 2.4.x. I do not
know if this will fix your problem. However, I have very good luck with
iptables and 2.4.x vs. 2.2.x.
Trever Adams
On Tue, 2002-01-08 at 16:02, Jacek Popławski wrote:
> I have simple 486 server with:
> - 2 ISA ethernet cards (eepro.o)
> - ppp connection to Internet
> I installed 2.4.17 (then 2.4.18-pre2) there, and discovered, that two connected
> workstations has very bad Internet connection (for example it was impossible to
> watch huge www pages or download pictures, edonkey/kza transfers were small).
> So i tested:
> - WWW speed on server -> OK (every page opens without problems)
> - scp transfer between server and workstations -> OK (more than 100KB/s)
> There is squid installed on my server. But even if I used it on workstation -
> WWW still works bad! Looks like something was really bad with MASQ. But
> everything was OK on much faster (k6-2 500) system.
>
> So I installed 2.2.20 - and all problems disappeared!
>
> I am almost sure I compiled similiar stuff to every kernel, there was exactly
> the same ipchains rules and route. How can I check what was bad with 2.4.x ?
prev parent reply other threads:[~2002-01-09 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 21:02 2.2.20 vs 2.4.17 on 486 server Jacek Popławski
2002-01-09 2:59 ` Trever L. Adams [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=1010545201.1258.1.camel@aurora \
--to=tadams-lists@myrealbox.com \
--cc=jpopl@interia.pl \
--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