From: Cameron Kerr <cameron.kerr@paradise.net.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] Hardware reqs for 10Mbps forwarding and shaping.
Date: Tue, 15 Apr 2003 12:12:18 +0000 [thread overview]
Message-ID: <marc-lartc-105040881412423@msgid-missing> (raw)
Greetings.
Environment:
50ish client PCs running Windows XP
10Mbps internet connection
Primary application is internet gaming and some web browsing.
I would like to create a Linux based solution which would provide
network monitoring services, and traffic shaping to prioritise
interactive traffic.
What kind of hardware would I need to use to be able to forward at
10Mbps, with low latency? Has anyone done such a demanding chore with
LARTC?
Ideally I'd like to use a bridged solution, so if it screws up, the user
can simply unplug the cables, and join then with a cable joiner. Is this
just asking for trouble? I know I would have to use 2.5.47???, which I'm
not really familiar with, how stable is 2.5 ATM?
I also have a query about scheduling. I'm thinking that it would be
unwise to use things like preemptive scheduling, since that's more for
user-space apps, not kernel ops. Am I right in thinking this?
Many thanks. I'm trying out LARTC with an old 4/66, but installing takes
bloody ages (Debian)
--
Cameron Kerr
Email: cameron.kerr@paradise.net.nz
Website: http://nzgeeks.org/cameron/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-04-15 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 12:12 Cameron Kerr [this message]
2003-04-15 13:28 ` [LARTC] Hardware reqs for 10Mbps forwarding and shaping Stef Coene
2003-04-15 13:55 ` Jay Wineinger
2003-04-15 13:55 ` Jay Wineinger
2003-04-15 16:52 ` Stef Coene
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-105040881412423@msgid-missing \
--to=cameron.kerr@paradise.net.nz \
--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.