From: Nikolay Kichukov <hijacker@oldum.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Simple Rule to Cap P2P Uploads
Date: Sat, 01 Jul 2006 13:53:49 +0000 [thread overview]
Message-ID: <1151762030.6342.4.camel@ccja.localhost> (raw)
In-Reply-To: <978458167.3856.1.camel@hpa.oldum.net>
Hi Mathew,
your adsl uplink is 64000 bps, correct?
102400kbps > 64kbps
3kbps != 3KB/sec
Another point, tc syntax is 102400kbit, not 102400kbps(as far as I
tested that).
3KB = 3*8 kbit
Test that and let us know if this helps.
-Nik
On Wed, 2006-06-28 at 09:50 -0700, Mathew Brown wrote:
> Hi,
> I'm new at traffic control and was reading up on HTB and using it to
> put an upper limit on traffic. I have a 256k DSL with 64k upload
> (which translates to about 5/6KB uploads). The machine running the
> P2P applications keeps filling up the 64K so my browsing from other
> machines in the network ends up being very slow. Since there are
> several P2P applications, I wanted to set the entire upload cap to
> something like 3KB/s so it doesn't disrupt browsing. However, I would
> also like to ssh and scp from this machine without having an upload
> cap. The machine has a single interface to the network: eth0. I
> tried the following tc lines but it appears to affect both the P2P
> traffic and my ssh traffic, resulting in a very slow ssh sessions:
>
> tc qdisc add dev eth0 root handle 1: htb default 3
> tc class add dev eth0 parent 1: classid 1:1 htb rate 102400kbps ceil
> 102400kbps
> tc class add dev eth0 parent 1:1 classid 1:2 htb rate 102400kbps ceil
> 102400kbps
> tc class add dev eth0 parent 1:1 classid 1:3 htb rate 3kbps ceil 3kbps
> tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip
> dport 22 0xffff flowid 1:2
>
> Any ideas? Thanks for your time.
>
>
> ______________________________________________________________________
> Do you Yahoo!?
> Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
Когато сме щастливи, сме добри.
Но когато сме добри, не винаги сме щастливи...
-Оскар Уайлд
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-07-01 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 17:56 [LARTC] Simple Rule to Cap P2P Uploads Nikolay Kichukov
2006-06-28 16:50 ` Mathew Brown
2006-07-01 13:53 ` Nikolay Kichukov [this message]
2006-07-04 13:30 ` Mathew Brown
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=1151762030.6342.4.camel@ccja.localhost \
--to=hijacker@oldum.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.