All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Nychis <gnychis@cmu.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] any alternative to netem drop? slow
Date: Fri, 21 Apr 2006 04:54:51 +0000	[thread overview]
Message-ID: <4449317B.5020300@cmu.edu> (raw)

Hi,

I was wondering if there is any alternative to netem drop probability... 
the reason I ask is that whenever I turn it on I get about 500KB/sec 
less throughput with 0% packet loss

The caveat is that it must work with 2.4.32 :)

Thanks!
George


Jason Boxman wrote:

>On Thursday 20 April 2006 22:19, Francisco wrote:
>  
>
>>L7 filter works very well too:
>>http://l7-filter.sourceforge.net/
>>
>>Although I didn't try it with sip, I use it to control my P2P and server
>>applications and have a very usable ADSL link at almost 100% utilization of
>>my upstream.
>>    
>>
>
>Does any of that include eMule traffic?  I stopped having success with eMule 
>protocols and L7 a year or two ago and the pattern hasn't been updated in 
>ages.
>
>  
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2006-04-21  4:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4449317B.5020300@cmu.edu \
    --to=gnychis@cmu.edu \
    --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.