All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [LARTC] Simple Rule to Cap P2P Uploads
@ 2001-01-02 17:56 Nikolay Kichukov
  2006-06-28 16:50 ` Mathew Brown
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Nikolay Kichukov @ 2001-01-02 17:56 UTC (permalink / raw)
  To: lartc

Hello Mathew,
Yes, it is all clear and your setup should work provided you changed the
few tiny bits I suggested.

Best,
-Nik

В вт, 2006-07-04 в 06:30 -0700, Mathew Brown написа:
> Thanks for your reply Nikolay.  I feel my first post was somewhat
> unclear.  I hope the following information clears things up a little
> more:
> 
> 1) The machine that I am trying to run do tc on has a single interface
> that connects it to the the rest of the network.
> 
> 2) I sometimes have to ssh and scp files from that machine.
> 
> 3) The machine runs various P2P applications.  I don't want the sum of
> their uploads to exceed 3 KB/s.
> 
> 4) As you mentioned, my ADSL uplink is 64000 bps
> 
> 5) The machine that I have tc running on and the machine with the P2P
> uploads are the same machine.
> 
> Thanks for your comments.  I'll try to check out the kbps vs. kbits.
> But is the idea of what I'm trying to do now more clear?
> 
> Nikolay Kichukov <hijacker@oldum.net> wrote:
>         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
>         -- 
>         ������ ��� ��������,
>         ��� �����.
>         �� ������ ��� �����, ��
>         ������ ��� ��������...
>         -����� �����
>         
> 
> 
> 
> 
> ______________________________________________________________________
> Yahoo! Music Unlimited - Access over 1 million songs. Try it free. 

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [LARTC] Simple Rule to Cap P2P Uploads
  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
  2006-07-04 13:30 ` Mathew Brown
  2 siblings, 0 replies; 4+ messages in thread
From: Mathew Brown @ 2006-06-28 16:50 UTC (permalink / raw)
  To: lartc


[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 1435 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [LARTC] Simple Rule to Cap P2P Uploads
  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
  2006-07-04 13:30 ` Mathew Brown
  2 siblings, 0 replies; 4+ messages in thread
From: Nikolay Kichukov @ 2006-07-01 13:53 UTC (permalink / raw)
  To: lartc

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [LARTC] Simple Rule to Cap P2P Uploads
  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
@ 2006-07-04 13:30 ` Mathew Brown
  2 siblings, 0 replies; 4+ messages in thread
From: Mathew Brown @ 2006-07-04 13:30 UTC (permalink / raw)
  To: lartc


[-- Attachment #1.1: Type: text/plain, Size: 2978 bytes --]

Thanks for your reply Nikolay.  I feel my first post was somewhat unclear.  I hope the following information clears things up a little more:

1) The machine that I am trying to run do tc on has a single interface that connects it to the the rest of the network.

2) I sometimes have to ssh and scp files from that machine.

3) The machine runs various P2P applications.  I don't want the sum of their uploads to exceed 3 KB/s.

4) As you mentioned, my ADSL uplink is 64000 bps

5) The machine that I have tc running on and the machine with the P2P uploads are the same machine.

Thanks for your comments.  I'll try to check out the kbps vs. kbits.  But is the idea of what I'm trying to do now more clear?

Nikolay Kichukov <hijacker@oldum.net> wrote: 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
-- 
������ ��� ��������, ��� �����.
�� ������ ��� �����, �� ������ ��� ��������...
-����� �����



 		
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs.Try it free. 

[-- Attachment #1.2: Type: text/html, Size: 3479 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-07-04 13:30 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2006-07-04 13:30 ` Mathew Brown

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.