From: Thomas Kirk <thomas@arkena.com>
To: lartc@vger.kernel.org
Subject: [LARTC] building linux router with QoS what about performance
Date: Mon, 01 Oct 2001 13:41:49 +0000 [thread overview]
Message-ID: <marc-lartc-100194370102558@msgid-missing> (raw)
Hey Listmembers
Im currently looking into building a linuxrouter which has one
purpose. To divide bandwidth to networks. The setup will look like
this :
Cisco 7120/oc3/100mbit--eth0--eth1,2,3,4 etc etc
Im planning to use CBQ to divide bandwidth against the diffrent
network. Right now im trying to figure out what the hardware
requirments would be and how scaleable this solution will be? Have
anyone on this list tried to doing something equal this setup or have
experince with QoS on high bandwidth links?
Thanks in advance
--
Venlig hilsen/Kind regards
Thomas Kirk
ARKENA
thomas@arkena.com
Http://www.arkena.com
"[In 'Doctor' mode], I spent a good ten minutes telling Emacs what I
thought of it. (The response was, 'Perhaps you could try to be less
abusive.')"
(By Matt Welsh)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
reply other threads:[~2001-10-01 13:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100194370102558@msgid-missing \
--to=thomas@arkena.com \
--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.