From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hardware requirements
Date: Fri, 11 Jul 2003 11:44:10 +0000 [thread overview]
Message-ID: <marc-lartc-105792394813559@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105791819408788@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Fri, 11 Jul 2003 13:08:03 +0300
alexandru matei <alex@qb.ro> wrote:
: Hi,
: I want to make a dedicated bridging traffic control machine using
: ebtables and HTB. The requirements will be to shape a 10 Mbit link to
: 1000 users. Is anyone have experience regarding the needed (estimated)
: hardware for this (processor/memory/type of network cards) ?
Hey, Alex,
For a similar setup (except that users are doubled and I'm not using bridge),
I have a PIII/1GHz with two Interl EEpro100 cards. Works fine, at least for now.
The only problem I'm experiencing is with heavy udp traffic, f.e. Counter Strike
and Bnetd (Diablo, DiabloII, {Star|War}Craft) game play. Then the machine is reaching
some really high load averages, like 8 to 10. Have no idea how this
could be avoided.
I'd appreciate any suggestions.
--
________________________________________________________________________
So long, and thanks for all the fish!
Nickola
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-11 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 10:08 [LARTC] hardware requirements alexandru matei
2003-07-11 11:44 ` Nickola Kolev [this message]
2003-07-11 11:56 ` Catalin BOIE
2003-07-11 12:51 ` Nickola Kolev
2003-07-11 13:01 ` Catalin BOIE
2003-07-12 19:17 ` Leonardo Balliache
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=marc-lartc-105792394813559@msgid-missing \
--to=nikky@mnet.bg \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.