From: "Phill" <PedroPhill@seznam.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - shaping services and IP
Date: Sun, 21 Sep 2003 06:25:16 +0000 [thread overview]
Message-ID: <marc-lartc-106412567011525@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106386774113974@msgid-missing>
Hello,
> : CeilDouwnloadDC\x120 #max download speed for direct connect
>
> Is this a typographical error? "CeilDownloadDC" instead of what you have
> written?
YES, This is a mistake I know about. I have fixed it already. Sorry
> : #11-->Fast-WWW,telnet,ssh,ping,...
> : tc class add dev $LOCAL parent 1:1 classid 1:11 htb rate 100kbit ceil
> : ${CeilDownload}kbit prio 1 burst 15k quantum 100
>
> I don't think this is a good idea for a quantum size. I'd suggest a
> quantum of minimum MTU size.
Ok, I will raise it. I thought that if it is too big, it will take a larger time
to send the packets then.
I want the ping to be as small as possible (fast surfing and game playing-rulles
not added yet).
I guess that quantum 2000 is ok.
>
> : tc class add dev $LOCAL parent 1:1 classid 1:15 htb rate 2kbit ceil
> : ${CeilDownloadDC}kbit prio 5 quantum 1
>
> Did you meant to set r2q to 1? A quantum of one penalizes this class
> severely.
No, I wanted DC (Direct connect -P2P program?) not to eat my bandwidth,
to have the lowest priority. With this settings it almost stops. Is there
anything
else I could do for that. I really want it to stop sending data if some one is
useing the line.
Should I leave the quantum parameter,or change it to what?
> ( good idea to add the terminal sfq qdiscs )
> :
################################################################################
> : # Upload part ...
> :
################################################################################
> :
> : tc qdisc add dev $NET root handle 2: htb default 21
> :
> : tc class add dev $NET parent 2: classid 2:1 htb rate ${CeilUpload}kbit
ceil
> : ${CeilUpload}kbit
> :
> : #11-->Fast-everything...Default
> : tc class add dev $NET parent 2:1 classid 2:11 htb rate 90kbit ceil
> : ${CeilUpload}kbit prio 7 burst 15k
>
> Good! You should get decent interactive performance out of this class!
>
> : #12-->Slow-DC,edonkey upload
> : tc class add dev $NET parent 2:1 classid 2:12 htb rate 6kbit ceil
> : ${CeilUploadDC}kbit prio 8 burst 5k quantum 1
>
> Again, with a quantum of 1, you several penalize this upload. I would
> agree that this is a good class to penalize. There is no reason to give
> away your bandwidth, but this will limit the upload rate to an almost
> neglible rate.
The same problem as above. I dont want to give the upload speed to DC,
that's why the rate is small and cail too. I thought that if I set quantum small
it will be good too. Am I right?
BTW I meassured that the rate matches the CeilUploadDC parametr.
---------------
I have tweaked the script to this state and it works. Of course I want to fix
these mistakes. I am very glad, that you are helping me!!!
The next thing is, that I wanted to shape the traffic for each user.
Lets say I want to shape speed of one user with IP 192.168.2.10 to rate 32 ceil
64.
Is there a way how to implement it to this script? Because really I like this
script,
which helps interactive traffic and web browsing.
If you have some code you can send me, I will be very happy. Don't matter what
it is,
that's the best way to learn from. If you do send them please to my private
phill@seznam.cz. Thanks
Thanks for your help,
Phill
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-21 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 6:47 [LARTC] HTB - shaping services and IP Phill
2003-09-19 4:56 ` Martin A. Brown
2003-09-19 6:49 ` Phill
2003-09-19 6:57 ` Phill
2003-09-21 5:22 ` Martin A. Brown
2003-09-21 6:25 ` Phill [this message]
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=marc-lartc-106412567011525@msgid-missing \
--to=pedrophill@seznam.cz \
--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.