All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard <finbert@sbcglobal.net>
To: lartc@vger.kernel.org
Subject: [LARTC] noprioportsrc
Date: Mon, 29 Mar 2004 12:08:12 +0000	[thread overview]
Message-ID: <200403291208.12134.finbert@sbcglobal.net> (raw)

I've been trying to get wondershaper 1.1a to let me set NOPRIOPORTSRC, but I 
cannot get it to work properly.

If I leave NOPRIOPORTSRC blank, the uplink is limited to what I set it to.  
But if I put 

NOPRIOPORTSRC="80 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 
6893 6894 6895 6896 6897 6898 6899 6900"

to make my bitorrents and my http server not effect my traffic for gaming and 
other stuff, the traffic is no longer limited!  I have it set at 400uplink 
(on a 600kbps upload) and instead of it locking at ~400kbps upload like it 
does when I leave NOPRIOPORTSRC blank, it acts as if there is no traffic 
shaping on the line.

To make things more interesting, after running the wondershaper script 
(without anything in NOPRIOPORTSRC) I manually tried to issue the command:
tc filter add dev eth0 parent 1: protocol ip prio 15 u32 match ip sport 6881 
0xffff flowid 1:30
to try and make port 6881 have lower priority.  Before issuing this command, 
my upload remains a constant 50kb/s up, and once I hit enter, my upload jumps 
up as if the wondershaper is not even there.

Am I doing something wrong?  On a side note, Is there an easy way to span 
ports instead of manually typing them all out (like 6881-6900)?

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

             reply	other threads:[~2004-03-29 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 12:08 Richard [this message]
2004-03-29 21:31 ` [LARTC] noprioportsrc Richard
2004-03-29 23:15 ` Damion de Soto
2004-04-11 22:31 ` 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=200403291208.12134.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.