From: sebastien robart@h3d.com
To: lartc@vger.kernel.org
Subject: [LARTC] Bridging and traffic shaping
Date: Mon, 20 Nov 2000 09:13:32 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216958@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216955@msgid-missing>
<PRE>I use this one with a 2.2.16 : <A HREF="ftp://openrock.net/bridge/">ftp://openrock.net/bridge/</A> . but i don't
use qos.
in the mailing list, someone seem have problem with qos (but with 2.4)
<A HREF="http://openrock.net/pipermail/bridge/2000-November/000574.html">http://openrock.net/pipermail/bridge/2000-November/000574.html</A>
seb
Yusuf Goolamabbas wrote:
><i> Hi, I have a set of machines [Linux/BSD/Solaris] for which I want to
</I>><i> traffic shape their output. I don't want to change any network
</I>><i> configuration so I am considering placing a box in bridging mode in
</I>><i> front of them. Can traffic shaping work in this configuration
</I>><i>
</I>><i> In Linux 2.2.17, the Bridging config option tells you to download the
</I>><i> bridge configuration tools from
</I>><i> <A HREF="http://lrp.plain.co.nz/tarballs/bridgex-0.30.tar.gz">http://lrp.plain.co.nz/tarballs/bridgex-0.30.tar.gz</A> which returns a
</I>><i> 404.
</I>><i>
</I>><i> According to the Bridge mini-HOWTO, the configuration tools are
</I>><i> available on <A HREF="ftp://shadow.cabi.net/pub/Linux/BRCFG.tgz">ftp://shadow.cabi.net/pub/Linux/BRCFG.tgz</A> whose hostname
</I>><i> is not found.
</I>><i>
</I>><i> Is this the right approach or do I need to think of another solution ?
</I>><i>
</I>><i> Regards, Yusuf
</I>><i>
</I>
</PRE>
next prev parent reply other threads:[~2000-11-20 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 3:22 [LARTC] Bridging and traffic shaping Yusuf
2000-11-20 9:13 ` sebastien [this message]
2000-11-20 9:36 ` bert
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-98373938216958@msgid-missing \
--to=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.