From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Traffic shapper and bridge
Date: Tue, 09 Dec 2003 23:10:14 +0000 [thread overview]
Message-ID: <marc-lartc-107101152423944@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107100744018777@msgid-missing>
On Tuesday, 09 December 2003, at 16:01:44 -0600,
Viaris wrote:
> The university is like a ISP to give access to Internet to several
> faculties, but we want to restrict the traffic, we needed a traffic shaper
> to do this, I wanted to have something like (Packeteer INTEL NETSTRUCTURE
> 7370 aplication server) which it is a bridge where I not need IP for my
> networks cards.
>
First, don't try to compare a high-end product from Packeteer to what
you are able to achieve with Linux + iptables + tc + l7-filter + brctl +
ebtables + whatnot. Maybe hacking these and some more utilities together
you can get something similar to the commercial product, but maybe you
should take into account some other things apart from "technically feasible".
A recent Linux kernel compiled with bridge support, patched and compiled with
with ebtables (iptables for bridges), plus ip/tc, plus userspace
ebtables, plus l7-filter, plus quite a bit of configuration, plus a
good and fasta hardware, plus many spare hours to configure and maintain
everything is all what you need.
Try to be more specific, although the feature in Packeteer's products of
behave transparently when the box fails is not something you can do with
Linux, as far as I know.
Greetings.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.0-test10-mm1)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-12-09 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 22:01 [LARTC] Traffic shapper and bridge Viaris
2003-12-09 23:10 ` Jose Luis Domingo Lopez [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=marc-lartc-107101152423944@msgid-missing \
--to=lartc@24x7linux.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.