From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: Netfilter <netfilter@lists.samba.org>
Subject: Re: Speed Issues through NAT Firewall
Date: 09 Jul 2002 20:25:45 +0200 [thread overview]
Message-ID: <1026239145.804.56.camel@tux> (raw)
In-Reply-To: <200207091808.g69I8R810149@vulcan.rissington.net>
On Tue, 2002-07-09 at 20:08, Antony Stone wrote:
> On Tuesday 09 July 2002 6:57 pm, Travis Crook wrote:
>
> > The firewall on the DSL is an Athlon XP 1500+. The firewall on the ISP
> > line is a PII 333. I will check on the full/half duplex issue.
>
> That's a hell of a difference, and could conceivably account for the
> bandwidth. I'd say it depends on how much RAM you have in the PII/333 and
> how many connections you're trying to support.
No way a pII 333 is to slow to handle 2Mbit/s, my old 486 can handle
that easily. You would have to trash the conntrack hashtable with
multiple attacks to even have a chance of getting it that slow.
I also believe there's a duplex-mismatch somewhere, probably between the
firewall and the internal network.
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat
you with experience.
next prev parent reply other threads:[~2002-07-09 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 17:29 Speed Issues through NAT Firewall Travis Crook
2002-07-09 17:38 ` Ramin Alidousti
2002-07-09 17:59 ` Travis Crook
2002-07-09 18:28 ` Ramin Alidousti
2002-07-09 17:49 ` Patrick Schaaf
2002-07-09 17:57 ` Travis Crook
2002-07-09 18:08 ` Antony Stone
2002-07-09 18:25 ` Martin Josefsson [this message]
2002-07-09 18:49 ` Ramin Alidousti
2002-07-09 19:32 ` Antony Stone
2002-07-09 23:08 ` Travis Crook
2002-07-09 17:53 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 19:03 j davis
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=1026239145.804.56.camel@tux \
--to=gandalf@wlug.westbo.se \
--cc=Antony@Soft-Solutions.co.uk \
--cc=netfilter@lists.samba.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