From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] noprioportsrc
Date: Mon, 29 Mar 2004 23:15:17 +0000 [thread overview]
Message-ID: <4068AE05.1010808@snapgear.com> (raw)
In-Reply-To: <200403291208.12134.finbert@sbcglobal.net>
Hi Richard,
> I've been trying to get wondershaper 1.1a to let me set NOPRIOPORTSRC, but I
> cannot get it to work properly.
This may be the same problem i discovered a while ago when I used the wondershaper as
a base for my own rules. I've fonud trying to make bittorrent behave itself is quite
difficult.
The 3 classes have rates specified as UPLINK, 9*$UPLINK/10 and 8*$UPLINK/10
This means the sum of the 3 classes is greater than the parent.
You may want to specify the rates as something lower that add up to UPLINK, and then
specify the ceil value for each class.
> 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)?
I use iptables to change the TOS bit of any packets in that range, then make a u32
filter for those TOS bits.
regards,
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-29 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 12:08 [LARTC] noprioportsrc Richard
2004-03-29 21:31 ` Richard
2004-03-29 23:15 ` Damion de Soto [this message]
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=4068AE05.1010808@snapgear.com \
--to=damion@snapgear.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox