From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] traffic shaping with ebtables
Date: Wed, 09 Jul 2003 15:48:59 +0000 [thread overview]
Message-ID: <marc-lartc-105776579802391@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105775518821597@msgid-missing>
On Wednesday 09 July 2003 14:51, alexandru matei wrote:
> Did anybody succeed to make traffic shaping in&outbound on a bridge
> (ebtables)?
> Any pointer to such documentation? Or just an example script?
I know someone used ebtabes, but I have no documentation. As fas I know,
using ebtables is the same as using iptables.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-09 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 12:51 [LARTC] traffic shaping with ebtables alexandru matei
2003-07-09 15:48 ` Stef Coene [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-105776579802391@msgid-missing \
--to=stef.coene@docum.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox