All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard <finbert@sbcglobal.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Wondershaper stops limiting outbound traffic
Date: Wed, 28 Apr 2004 16:37:51 +0000	[thread overview]
Message-ID: <200404281637.51669.finbert@sbcglobal.net> (raw)

I have wondershaper to limit my upload at 400kilobits (my line is 600kbps).

I do a lot of torrent seeding and I dont want my pings killed when I'm 
uploading so I set low prority source ports as follows (by the way, I have 
bittornet to only use ports 6881-6910):

NOPRIOPORTSRC="6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 
6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 
6908 6909 6910"

Problem is, sometimes my upload will be limited to 50kb/s and others it'll be 
maxed.  This is with wondershaper running too!  (verified by ./wshaper 
status).

If I stop wondershaper (./wshaper stop) my outbound bandwith does nothing (as 
it's already maxed) but if I try to start it again, nothing happens again 
(yet ./wshaper status shows that wondershaper is installed).  If I comment 
out all the SRC ports that I want no priority for, and re-run wshaper, my 
outbound is once again limited to 50kb/s, but my pings are horrible because 
all bandwith has the same priority.

Some will ask why not use the torrents bandwith limitation....the answer to 
that is because it sucks.  I have it set to 50kb/s and instead of it sataying 
at 50, it fluctuates up and down and AVERAGES 50kb/s.  

What could be causing this problem when NOPRIOPORTSRC is set to de-prioritize 
torrents? 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-04-28 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 16:37 Richard [this message]
2004-04-30  9:07 ` [LARTC] Wondershaper stops limiting outbound traffic Andy Furniss

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=200404281637.51669.finbert@sbcglobal.net \
    --to=finbert@sbcglobal.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.