From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables vs tc
Date: Sat, 04 May 2002 07:38:35 +0000 [thread overview]
Message-ID: <marc-lartc-102049796724620@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102049083822072@msgid-missing>
tc being more universal (can do non-IP, rsvp, diffserv) but
more coomplex to understand. iptables are well known but
as name implies - IP only.
devik
On Fri, 3 May 2002, Chris Ellsworth wrote:
> 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/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-05-04 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 5:39 [LARTC] iptables vs tc Chris Ellsworth
2002-05-04 7:15 ` Stef Coene
2002-05-04 7:38 ` Martin Devera [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-102049796724620@msgid-missing \
--to=devik@cdi.cz \
--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.