All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth limiting
Date: Tue, 09 Apr 2002 12:52:23 +0000	[thread overview]
Message-ID: <marc-lartc-101835680928175@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216959@msgid-missing>


you can do the same with netfilter, with the relevant matches. it has to
be cleverly constructed yes, but it definitly is possible. you can use priorities
with connection marking.... very easy

i would like to know how tc drops packets, because if i drop consecutive packets
(over 10 or 20) in one connection, it gets reset by the other side. if i drop
packets randomly (50%), it works fine.



On Tue, 9 Apr 2002, Stef Coene wrote:

> On Tuesday 09 April 2002 01:51, Nigel Kukard wrote:
> > hrmmm, ok after trying out  "tc"  for the last week i've noticed it is
> > not even nearly as powerfull as netfilter.
> Netfilter is designed to filter the traffic and the packets.  Tc will manage 
> the outgoing queue and has nothing to do with netfilter.  
> They both will drop packets, but with netfilter you can specify the packets 
> (so you can create a firewall) while tc will drop packets to slow down the 
> sender.
> Tc is used to manage the bandwidth you can send (and in a special way you 
> receive).  Netfilter can also do rate-limiting, but it can't do it as 
> powerfull as tc.  Tc can share the bandwidth between classes, give packets a 
> higher priority, ...
> 
> Stef
> 
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-04-09 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  0:00 [LARTC] Bandwidth limiting Thomas
2000-11-22 16:35 ` Thomas
2000-11-22 23:35 ` Thomas
2002-04-08 23:51 ` Nigel Kukard
2002-04-09 12:44 ` Stef Coene
2002-04-09 12:52 ` Nigel Kukard [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-101835680928175@msgid-missing \
    --to=nkukard@lbsd.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.