From: "Chris Ellsworth" <cke@highlandshighspeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] iptables vs tc
Date: Sat, 04 May 2002 05:39:07 +0000 [thread overview]
Message-ID: <marc-lartc-102049083822072@msgid-missing> (raw)
Since monitoring this list and others i see people use both iptables
and tc to assign packets on a bridge to the correct class for
bandwidth control, what is the plus/minus of each?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-05-04 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 5:39 Chris Ellsworth [this message]
2002-05-04 7:15 ` [LARTC] iptables vs tc Stef Coene
2002-05-04 7:38 ` Martin Devera
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-102049083822072@msgid-missing \
--to=cke@highlandshighspeed.net \
--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.